#2102: Audit translated manual pages
--------------------------------------------+-------------------------------
 Reporter:  [EMAIL PROTECTED]  |        Owner:  [email protected]
     Type:  task                            |       Status:  new                
           
 Priority:  normal                          |    Milestone:  6.2                
           
Component:  BOOK                            |      Version:  SVN                
           
 Severity:  normal                          |   Resolution:                     
           
 Keywords:                                  |  
--------------------------------------------+-------------------------------
Comment (by [EMAIL PROTECTED]):

 Yes, the /dev/null idea as I described is flawed. I notice you did not
 comment about my first suggestion, of letting the users handle this on
 their own.

 A couple of questions just to help get me up to speed with mandb:

 Is this an LFS-specific issue? For instance, are there distros
 available that would not require this and the man pages would
 be considered "supported".

 Additionally, could one 'fix' the LFS installation so that the country
 that is currently unsupported could be made to be supported?

 I suppose what I'm looking for is a way that we can put this onus on
 the user and wouldn't require the editors to have to remember to run
 a script after updating each and every package, each and every time.

 Surely, there is some way to accomplish this. Another suggestion:

 Provide a crontab entry for users to automatically run a script (both
 provided on the locale issues page) which removes any files that may
 exist. I'm not saying my suggestions are the optimum solution, I'm
 just, as I've mentioned, interested in pushing this off on the users.

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/2102>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://linuxfromscratch.org/mailman/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to