Opened 24 years ago

Closed 23 years ago

Last modified 23 years ago

#5 closed defect (wontfix)

Packages install non-english man pages in /usr/share/man

Reported by: gerard@… Owned by: markh@…
Priority: normal Milestone:
Component: Book Version: 3.0-pre2
Severity: normal Keywords:
Cc:

Description

Attachments (1)

shadow-20001016.patch (821 bytes ) - added by nomis80@… 24 years ago.
This is the updated patch. It fixes both the man page problem and the previous problem which the previous patch fixed.

Download all attachments as: .zip

Change History (15)

comment:1 by gerard@…, 24 years ago

Summary: shadow password suite installs polish man-pages to /usr/share/man/plPackages install non-english man pages in /usr/share/man

Shadow password suite is one of them, net-tools is another. FHS compliance notes are probably needed as well to make that all proper.

comment:2 by gerard@…, 24 years ago

Owner: changed from gerard@… to lfs-book@…
Priority: lownormal
qa_contact: gerard@linuxfromscratch.orglfs-book@linuxfromscratch.org

comment:3 by nomis80@…, 24 years ago

Owner: changed from lfs-book@… to nomis80@…
Status: newassigned

by nomis80@…, 24 years ago

Attachment: shadow-20001016.patch added

This is the updated patch. It fixes both the man page problem and the previous problem which the previous patch fixed.

comment:4 by nomis80@…, 24 years ago

Resolution: later
Status: assignedclosed

There is an unforeseen problem. We can't clearly force the user into not installing foreign language man pages. But if we permit the installation of the man pages, then all the english pages (currently man[1-8]) would need to be in a subdirectory "en". The FHS dictates that and explains it in great lenght in section 4.11.5, version 2.2-beta. And it is a Good Thing(TM), since man will use these directories in case the localization environment variables are set.

So we should change every package and make it use /usr/share/man/en instead, for the man dir. Or, much more simply, we could move man* into en after the installation is over. Yes, I think that would be the best answer. But then we would need to somehow tell man to go into en. Dunno how to do that, but i know it's easy. man was designed to operate like that.

One last thing: the shadow patch (attachment 1) must not be applied.

comment:5 by gerard@…, 23 years ago

What are we going to do about this? Move all man pages to /usr/share/man/en, and has anybody figured out yet how to tell man to look in /usr/share/man/<language>?

comment:6 by nomis80@…, 23 years ago

Resolution: later
Status: closedreopened

comment:7 by nomis80@…, 23 years ago

Owner: changed from nomis80@… to lfs-book@…
Status: reopenednew

comment:8 by markh@…, 23 years ago

Owner: changed from lfs-book@… to mark-lfs@…
Status: newassigned

I'm working on this (doing a cvs build and figuring out how to get packages to install man pages to /usr/share/man/en) I think that although this is more convoluted, it's probably the best solution. I think we should at least try it. I'll also figure out how to configure man to use those dirs while I'm at it.

comment:9 by markh@…, 23 years ago

I've been playing with this for a while now. We can make all the packages (I think) install man pages to /usr/share/man/en/man*

The thing is, this'll require an option to be added to ./configure or a sed command for each package. This seems to be a bit excessive. Maybe we could use Simon's suggestion to move /usr/share/man/man* to /usr/share/man/en/man* instead?

We'll also have to add a comment for when users install their own packages. I'm looking at the config issue for man at the moment.

To be honest, I'm doubtful about the value of this change compared to the gains. For starters, not a great number of the base LFS packages come with foreign manual pages anyway.

Comments? I think this should go to lfs-discuss for discussion.

comment:10 by gerard@…, 23 years ago

Yes, let's move it to lfs-discuss. I also agree it's probably not worth the effort so my vote is to just drop the matter.

comment:11 by markh@…, 23 years ago

Resolution: later
Status: assignedclosed

Nobody seems to care much about this so we'll drop it for now. Maybe we can come back to it in the future.

comment:12 by gerard@…, 23 years ago

Let's close it for now

comment:13 by gerard@…, 23 years ago

Resolution: later
Status: closedreopened

Reopening but closing (and change it's resolution to WONTFIX instead of LATER)

comment:14 by gerard@…, 23 years ago

Resolution: wontfix
Status: reopenedclosed

nobody seemed interested in it, too much work, not worth the gain

Note: See TracTickets for help on using tickets.