On 4/26/07, Randy McMurchy <[EMAIL PROTECTED]> wrote: > Dan Nicholson wrote these words on 04/26/07 09:20 CST: > > > Except that I also have to make a copy on anduin and ensure that it's > > still right. If I put it in auxfiles, then it magically appears in the > > anduin repo, and I can easily see any changes locally in svn. So, I > > guess it's not so much the version control I'm after, but the > > convenience. > > I guess I'm confused as to what you are looking to do. I don't even > *use* this auxfiles section, nor have I ever even downloaded that > repo as it is below the BOOK in the tree.
The main reason we added it was because of Xorg. There's vital information in the wget lists such as the individual package versions. Previously, this was just a file sitting on anduin. Not only were package version changes invisible, but if something happened to those files, whoops. Now, whenever I update firefox, I have to make a change to the embedded mozconfig file in firefox.xml. Then I have to ssh into anduin, make a copy of the file and make the same change there since we offer the opportunity to just download it. It would be awfully convenient for me to just edit a file in auxfiles/ and have it show up at the right location on anduin. I could also trivially see in svn that my changes were the same, too. Have a look at the files in files/BLFS/ on anduin. The compressdoc script jumps right out as something I'd rather have in the repo. In fact, I've been planning on that for a long time. Does that make sense? -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
