#2073: Package management page is oversimplified
--------------------------------------------+-------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  [email protected]
     Type:  enhancement                     |       Status:  closed             
          
 Priority:  normal                          |    Milestone:  7.0                
          
Component:  Book                            |      Version:  SVN                
          
 Severity:  normal                          |   Resolution:  fixed              
          
 Keywords:                                  |  
--------------------------------------------+-------------------------------
Comment (by [EMAIL PROTECTED]):

 > LFS & BLFS do mention configuration files that may need to be edited

 Well, they miss some files, or mention them on a different page. E.g.,
 /etc/inputrc (which is, in fact, a configuration file for Readline) is
 mentioned on the "Creating the /etc/inputrc File" page, while
 /etc/scsi_id.config is not mentioned at all. If the packager forgets to
 mention a file, it will be overwritten without backup on a package
 upgrade.

 Also, for creation of RPM packages, one must enumerate all files for which
 a changed MD5 sum is not an error.

 As for repositories, some package managers (most notably, apt) are meant
 to be used only with repositories. Nobody uses dpkg directly. Thus, it is
 natural to mention the task of repository creation.

 I am not suggesting that these tasks are solved by LFS. It is just
 necessary to warn the reader that such tasks exist and there are no hints
 about the possible errors, and that "it's all in my head" and "I rebuild
 everything every 24 hours" may well be the preferred solutions.

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2073#comment:3>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to