#2633: Doc directory for udev
-----------------------+----------------------------------------------------
 Reporter:  jhuntwork  |       Owner:  lfs-b...@…                   
     Type:  defect     |      Status:  new                          
 Priority:  normal     |   Milestone:  6.7                          
Component:  Book       |     Version:  SVN                          
 Severity:  normal     |    Keywords:                               
-----------------------+----------------------------------------------------

Comment(by br...@…):

 Hmm.

 Given what those docs are (at least as of udev-146... I need to
 upgrade...), I think they should either stay where they are, or be
 deleted.

 They're libudev API HTML-format docs, similar in format to what's stored
 in /usr/share/gtk-doc/html/gtk/index.html by GTK+.  (Those same docs are
 available at http://library.gnome.org/devel/gtk/stable/ if you don't have
 GTK+ installed.)  /usr/share/gtk-doc is really the right tree for that
 stuff.

 It looks like there isn't really anything in any path matching
 /usr/share/doc/udev* anymore, except for files we put there as of -146.
 Looking through Makefile.am in a synced-to-upstream udev git tree also
 shows only one extra (keymap) dropping anything into docdir (dist_doc_DATA
 = extras/keymap/README.keymap.txt), but that's inside an "if
 ENABLE_EXTRAS" check, so we don't build it anyway.

 We probably need to update the installation instructions; if udev isn't
 dumping anything into --docdir, there's really no point in giving it that
 argument.  But someone (me, if I get more than 20 minutes or so here
 anytime soon) should probably verify that it really doesn't dump anything
 there the way we configure it today.

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