On Fri, 2011-10-07 at 13:28 -0700, Jeremy Huddleston wrote: > >> I would prefer passing in paths to my local git checkouts over > section/module.
I think I understand better now. The paths are relative paths to where the script is invoked. The script can cd down to the last subdir and interrogate the git module for what it needs to know. Hopefully it can find the section from there. This is what Alan was trying to do with the url and sed. That would be fairly flexible and easy. It could even be an absolute path. The usage statement could be: Usage: $basename [options] path... Where "path" is a relative or absolute path to a git module. Options: [...] > >> You should still be able to do the same -<version> foo by checking > if the argument > >> is a dir, if not, chop off the -* and check again. > > > > Sorry I don't get it. Can you give me an example? > > $ git clone ssh://git.freedesktop.org/git/xorg/app/xedit > $ git clone ssh://git.freedesktop.org/git/xorg/lib/libX11 > > do some stuff in both > > publish.sh libX11 xedit > > or > > publish.sh libX11-1.10.0 libX11-1.9.4 libX11-1.8.8 xedit > > > An entry such as lib/private_libX11 will work. I just need "lib" to > get > > the section and there should be > > either no subdir or only one subdir. I am basically following the > module > > url: > > > > git://anongit.freedesktop.org/xorg/ ==> lib/libX11 > > or git://anongit.freedesktop.org/xorg/ ==> xserver > > > > What would be the structure of your "local git checkouts"? > > As above. I just dump them all into one directory. I rename > font/util to font-util and util/macros to util-macros to avoid > confusion. I also have multiple xserver-*/ dirs at common checkouts > to avoid rebuilding when going between versions.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
