On Wed, Nov 25, 2009 at 12:50:26PM -0500, Joey Hess wrote: > Yann Dirson wrote: > > After using "mr bootstrap" we end up with a conventional-looking tree > > with a .mrconfig at its root (similar to what we get from a "git/hg > > clone"). It would be really convenient to consider this a workspace > > of some sort, so that, much like with git or hg, mr would look upwards > > into parent repositories to find the first .mrconfig and use it. That > > would avoid having to specify -c each time. > > > > Well, I guess a well-crafter include command in ~/.mrconfig could do > > the job, and I'll probably end up writing one if I finally decide to > > use mr. > > Yes, all you need is something like this in ~/.mrconfig: > > [some/workspace] > chain = true > checkout = : # or optionally, command to really check it out > > It might make sense indeed to have mr bootstrap add such stanzas for > you.
Hm, I'm not sure adding lines for each repo is a good idea (even automatically). This can cause unwanted effects, eg. when a workspace gets removed without the lines being purged, and some other files comes in the way later by chance. > Or you can use -p to search up the directory tree for a .mrconfig and > use it. Oh, looks like I missed this option - it seems to provide exactly what I need. > If you'd like to alias mr = mr -p Rather than that, what about adding support for making it the default in ~/.mrconfig ? Well, not exactly that, since that would imply "read ~/.mrconfig first, and then if this flag is specified, search for an additional .mrconfig upstairs." - that would also match the behaviour of other tools (like git's ~/.config and .git/config). > , I suggest first doing this > to enable the trust system, which will prevent injected untrusted mrconfig > files from running arbitrary commands: Well, couldn't the problem about trusting files be solved in a less intrusive way ? I would suggest to refuse loudly to use a .mrconfig with improper write permissions, and to stop recursing upstairs as soon as we encounter a directory with wrong owner or improper write permissions (and maybe to stop if reaching ~ even if it has correct permissions, to avoid re-reading ~/.mrconfig). Wouldn't that be sufficient ? Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
