On Mon, 2007-04-23 at 14:02 +0200, Ramon van Alteren wrote: > To be clear, I'm willing to do all the work to get this implemented, I > already hacked up our current catalyst-2.0.1 install to do just this. > It is however rather hackish and i would like to get this in the main > tree. The patch would be against current svn. > > I'm curious about a number of things: > > * Would this functionality be useful for more people on the list ?
What is stopping you from using an absolute path on the machines? If you control them, standardize on a checkout location. > * Would this patch ever stand a chance of getting integrated ? Not unless we can come up with some reason why we would need to add the code complexity to catalyst. Essentially, there would have to be a few use cases that would absolutely prohibit using absolute paths, otherwise I don't see a reason for changing it. This has been brought up before and always shot down simply because nobody could ever give me a reason why an absolute path wouldn't work for them and only a relative would. If you can show that what you want to do cannot be accomplished with the current code and absolute paths, then it would be accepted. Remember that simply making something easier for you isn't a valid reason for hacking up catalyst internals that much. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation
signature.asc
Description: This is a digitally signed message part
