RE: Repo package
Pursehouse, David
Hi,
> Repo auto-update itself with his origin repository [1] every time the user run a sync command.
Another way to get around this is to mirror git-repo in a local repository, without tags, and then add “insteadOf” settings in the .gitconfig file:
[url "ssh://us...@path.to.your/git-repo:29418/tools/repo"]
insteadOf = https://code.google.com/p/git-repo/
Regards,
David
From: repo-d...@googlegroups.com [mailto:repo-d...@googlegroups.com] On Behalf Of Mickaël Salaün
Sent: Monday, November 19, 2012 8:33 AM
To: repo-d...@googlegroups.com
Subject: Repo package
Hi,
Repo auto-update itself with his origin repository [1] every time the user run a sync command.
Does a Repo user should be free to choose his update mechanism?
What do you think about being able to package Repo and use a general purpose updater (e.g. APT)?
For my part, I prefer being able to *choose* which updating system I want, and let distributions packagers handle this task as they does with most softwares.
It's also an important point if you want to propose Repo to a wider range of developers. It seems a good idea to make it natively available in distributions.
I have done some changes in that direction :
* absolute symlinks: https://gerrit-review.googlesource.com/37961
* without repository: https://gerrit-review.googlesource.com/37962
* no clone: https://gerrit-review.googlesource.com/37681
* Makefile: https://gerrit-review.googlesource.com/39260
The idea is to keep the current behavior (i.e. auto-updating for every sync) but to allow packagers to easily embedded Repo in a common package (DEB, RPM, tarball, etc.). The behavior change only occurs when you remove the ".git" directory like with: make install PREFIX=~/usr
Regards,
Mickaël
On 11/10/2012 22:30, Conley Owens wrote:
> Conley Owens has posted comments on this change.
>
> Change subject: Use relative or absolute hook symlinks
> ......................................................................
>
>
> Patch Set 5:
>
> """This commit only change the Repo behavior when the command is not in
> the parents directory, but elsewhere. This will change nothing for the
> current use."""
>
> I recognize that, but it adds code complexity for the sake of an
> unsupported use case.
>
> """About the self update thing, it's only from the commit I2f7e49cc.
> Again, there is no Repo behavior change for the current use. The commits
> only affect installation without the ".git" directory, which happen only
> in a manual way (i.e. git archive). Anyway, without this commit, Repo
> will crash if there is no ".git" directory, so it's more a fix than
> feature ;)"""
>
> Same comment here. Currently, there is a design assumption that repo
> should always be able to update itself regardless of where it is installed.
>
> """Theses commits are necessary before being able to package Repo."""
>
> I'm not sure that being packageable is that desirable of a feature.
>
> I appreciate the work you've put into these changes, but I suggest that
> you start a thread on repo-d...@googlegroups.com and see if others in
> the community would like to see these use cases supported and if other
> repo authors are willing to abandon the design assumption that repo will
> self-update.
>
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en