#2205: Blanket notes for updated builds (SVN-DJL-20080825)
----------------------------------------+-----------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  [email protected]
     Type:  task                        |       Status:  new                    
      
 Priority:  normal                      |    Milestone:  Future                 
      
Component:  Book                        |      Version:  SVN                    
      
 Severity:  normal                      |   Resolution:                         
      
 Keywords:                              |  
----------------------------------------+-----------------------------------
Comment (by [EMAIL PROTECTED]):

 Replying to [comment:8 [EMAIL PROTECTED]:
 >
 > Is there a way to automate downloading and incorporating the patches?
 Rolling up the current list seems to be a lot of work that will need to be
 redone with every one of the relatively frequent patches.
 >
 > I did this for autofs in BLFS and it should be considered for vim.

 I ought to write this before.

 This is not possible, unless:

 a. we are going to extend the instructions to extract also the extra
 sources, otherwise there are going to be patches that don't apply or

 b. in the hypothetically given loop, we are going to blacklist some
 patches or

 c. maintain an external script to filter also some patches based on their
 header

 I am sure most people here don't want to add bloat in their disk to
 extract mac, dos, vms or windows stuff, so I don't give many chances for
 the first possibility.
 b is possible, but we still have to keep updated the list with the
 blacklisted patches, if we don't want to have broken instructions and it's
 a little bit ugly.
 c is possible but it's also an extra step, so again there is bloat that
 people might want to avoid

 However and if we follow one of the above solutions or something else that
 I don't have in mind right now, this will sets a precedent, with the
 meaning that:

 - we are going to provide instructions for users, to apply patches without
 testing beforehand by an editor

 - the codebase is going to be different from build to build, so support
 (especially) and testing is going to be also problematic

 Another problem; what we are going to do in the case of a stable book
 release?

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2205#comment:15>
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