Alexander E. Patrakov wrote these words on 08/16/07 00:51 CST: > Slackware packages never ship configuration files that are supposed to > be modified by end users. Instead, such configuration files are shipped > with the .new extension, and a post-installation script handles this.
This to me is way, way beyond the scope of what we do. If it ends up that we want to do something like this, I would hope it would be a separate branch, with the main thrust continuing with what we currently do. To me, there simply isn't enough development staff to attempt to be a distribution. On the LFS side, with 2-4 devs, it would be doable, in BLFS right now with the current staff, impossible. Just offering thought, so don't think I'm totally being negative, nor arguing against the idea. I'm just thinking that it adds such an enormous effort on top of what we already do, that it would soon seem insurmountable trying to keep up. -- Randy rmlscsi: [bogomips 1003.22] [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] 00:59:00 up 4 min, 1 user, load average: 0.24, 0.42, 0.19 -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
