On Wed, 27 Feb 2013 11:42:54 +0000 Tom Hacohen <tom.haco...@samsung.com> wrote:
> On 27/02/13 11:35, David Seikel wrote: > > On Wed, 27 Feb 2013 11:28:01 +0000 Tom Hacohen > > <tom.haco...@samsung.com> wrote: > > > >> On 27/02/13 11:19, David Seikel wrote: > >>> On Tue, 26 Feb 2013 17:47:09 +0000 "Eoff, Ullysses A" > >>> <ullysses.a.e...@intel.com> wrote: > >>> > >>>> jhbuild (https://live.gnome.org/Jhbuild) is another tool that can > >>>> do this too. > >>>> > >>>> U. Artie > >>>> > >>>>> -----Original Message----- > >>>>> From: Tom Hacohen [mailto:tom.haco...@samsung.com] > >>>>> Sent: Tuesday, February 26, 2013 9:21 AM > >>>>> To: Enlightenment developer list > >>>>> Subject: [E-devel] Git: Multiple repositories cloning helper > >>>>> > >>>>> Hey all, > >>>>> > >>>>> Now that everything is nicely split to small repositories, it's > >>>>> "more work" to clone all the repositories. > >>>>> There's a tool Google has created for Android called "repo" > >>>>> (http://source.android.com/source/version-control.html), that > >>>>> manages multiple repositories. > >>>>> > >>>>> Alternatively, if you don't like the "repo" tool, you can use a > >>>>> small tool we wrote. > >>>>> Our small tool helps you clone, pull (--rebase) updates, and run > >>>>> arbitrary commands (like make and make install). > >>>>> > >>>>> You can get it from this repo: > >>>>> git://git.enlightenment.org/devs/tasn/git_multi.git > >>>>> > >>>>> README (for those that are too lazy to open the README from the > >>>>> repo): This is a small script that helps pulling, cloning and > >>>>> running arbitrary commands in multiple repositories. Designed to > >>>>> help with the EFL. > >>>>> > >>>>> You should modify the REPOS and DEV_ACCESS at the top of the > >>>>> script before using. > >>>>> > >>>>> Usage examples: > >>>>> Clone all repos: > >>>>> ./git_multi.sh clone > >>>>> > >>>>> Update all repos (pull --rebase): > >>>>> ./git_multi.sh pull > >>>>> > >>>>> Fetch (without rebasing or merging or anything): > >>>>> ./git_multi.sh run "git fetch" > >>>>> > >>>>> Make and install (with sudo): > >>>>> ./git_multi.sh run "make && sudo make install" > >>>>> > >>>>> Regards, > >>>>> The SVN Elimination Team. > >>> > >>> From what I can tell after some research, all of these need > >>> someone on the server end to create a list of all the repos, or to > >>> create such a list manually on the client end. There does not > >>> seem to be any AUTOMATED way of collecting the list of all the > >>> repos, short of scraping the http://git.enlightenment.org/ web > >>> page, which might itself be manually created? Git seems to not > >>> provide this sort of functionality. Someone correct me if I'm > >>> wrong please. > >>> > >>> Or to put it more simply, a way to just clone every single repo, > >>> without any manual work at either end. Including new ones that > >>> get added at random times, possibly without any announcement. > >>> > >>> There's over three dozen now, manual work is just not gonna cut > >>> it. > >> > >> That's not what those tools are for. No one should ever want to > >> clone all the git repositories on the server. The mess we used to > >> have in svn is a disease we managed to cure, not something we > >> would like to bring back. > > > > I think this cure is worse than the disease then, though I have no > > idea what aspect of it you think is a "disease". I want to clone > > them all, it's entirely possible someone else might want to clone > > them all. Or at least clone some of the ones that you don't think > > are needed. > > Please tell me why you'd need 10 photo viewers that cloned into your > box. I'm quite interested. What possible reason would you have to > clone them all? Clone some of the ones I don't think as needed: you > can add how many repos you'd like to the script I wrote, or clone > them "manually". The failure of your imagination is not my problem. BTW, a decent build bot would also want to automatically figure out all the repos, coz that's one less thing to have to manually configure. > >> Those solutions only provide specific components, that's the whole > >> idea, only the needed ones. > > > > How do people know what is needed, if there's no automatic list to > > choose from? > > They get all the core ones, which are the core essentials, and then > get the extra stuff they might want. Or read about it in the website. > > > > > Is http://git.enlightenment.org/ compiled automatically? > > Yes, it's automatically generated. See? It's much easier to answer my question than to tell me that I don't want what I said I want. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
