Bruce Dubbs wrote these words on 01/24/07 14:53 CST: > IMO it doesn't make sense to try to completely automate this. It > doesn't happen that often and its very hard to think of everything that > can happen in advance.
I agree with everything you said. However, none of it addresses the situation I'm trying to identify. I'll try and simplify: To download patches from the SVN book we use the URL: http://www.linuxfromscratch.org/patches/blfs/svn/patch_name from the 6.1 book we use: http://www.linuxfromscratch.org/blfs/downloads/6.1/patch_name I think it is screwy to have some patches in: .../patches/blfs and others in .../blfs/downloads/ My thinking is that for consistency the patches should be in: .../patches/blfs/{svn,6.1,stable,whatever_else} or .../blfs/downloads/{svn,6.1,stable,whatever_else} Not that it really matters, but why store everything all over the place, when a consolidated area seems to be more, um, organized? Lastly, and to reiterate, this doesn't have anything to do with automating. It has to do with organization. -- Randy rmlscsi: [bogomips 1003.26] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 14:57:00 up 14 days, 15:11, 1 user, load average: 0.15, 0.10, 0.07 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
