On Mar 14, 2014, at 3:13 AM, Christian Brueffer <bruef...@freebsd.org> wrote:
> On 3/14/14 2:54 AM, John-Mark Gurney wrote: >> John Nielsen wrote this message on Thu, Mar 13, 2014 at 16:28 -0600: >>> On Mar 13, 2014, at 10:19 AM, John-Mark Gurney <j...@freebsd.org> wrote: >>> >>>> Author: jmg >>>> Date: Thu Mar 13 16:19:36 2014 >>>> New Revision: 263110 >>>> URL: http://svnweb.freebsd.org/changeset/base/263110 >>>> >>>> Log: >>>> remove link to the missing AMD Geode LX SB man page... we can add it >>>> back once someone cares enough to write one.. >>> >>> You mean like this one? >>> http://svnweb.freebsd.org/base/head/share/man/man4/man4.i386/glxsb.4 >> >> The problems of checking on an amd64 box... :( >> >> Actually, how are we suppose to handle links to arch dependant man >> pages in arch independant man pages? I did this check on an amd64 box, >> so the page glxsb didn't get installed... Should we just always >> install these man pages on all arches then? Or are we fine w/ >> references to non-existant pages (on some arches)? >> >> Or should glxsb.4 be moved to an arch independant dir? >> > > I wonder if it makes sense to keep arch-dependent man directories at > all. I.e., if I prepare an ARM disk image on my amd64 laptop, I really > want to have the arm manpages available on that amd64 box. > > Does anyone see a reason not to move man4/man4.${ARCH}/*.4 to man4? > We're talking about 60 manpages here, so space is not really an issue. Historically there was the separation because xp on one platform might be radically different from xp on another platform. The other reason was confusion because it wasn’t always clear if device foo actually worked on platform X. Do we have any collisions like that? If so, we need to resolve those first. Also, it would be good to tag the ones that are arm specific as such somehow. Warner _______________________________________________ svn-src-head@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
