[arch-dev-public] [signoff] man-db 2.5.3-1 replacing man
I've built man-db based on the package in community adding some changes I have found in a very good written page in the LFS book: http://www.linuxfromscratch.org/lfs/view/6.4/chapter06/man-db.html You can read there all about man page encoding and the expected locations and how to recode them. Therefor I have added the LFS recode script. This will allow us to recode broken man-pages when we will get bugreports. This should improve the current situation a lot. Maybe we should write down later into the packager guide how to fix broken manpages, maybe even into the public wiki. I didn't want to add a new system user "man" as the community package does. It seems to run fine without serious security concerns for me. If you think different feel free to drop a mail here. It's not critical to create a database after installation. So I left out any install message. The cronjob will do this on its next run. You can surely run mandb manually to see how it goes. All local tests have worked well. So I start a signoff thread now. -Andy
On Wed, Feb 18, 2009 at 4:10 PM, Andreas Radke <a.radke@arcor.de> wrote:
I've built man-db based on the package in community adding some changes I have found in a very good written page in the LFS book:
http://www.linuxfromscratch.org/lfs/view/6.4/chapter06/man-db.html
You can read there all about man page encoding and the expected locations and how to recode them. Therefor I have added the LFS recode script. This will allow us to recode broken man-pages when we will get bugreports. This should improve the current situation a lot.
Maybe we should write down later into the packager guide how to fix broken manpages, maybe even into the public wiki.
I didn't want to add a new system user "man" as the community package does. It seems to run fine without serious security concerns for me. If you think different feel free to drop a mail here.
It's not critical to create a database after installation. So I left out any install message. The cronjob will do this on its next run. You can surely run mandb manually to see how it goes.
Holy smokes, did you try running the cron job? It generates an absurd amount of output, so for those people that get email when cron jobs produce output on stdout/stderr, this might be a bit much. Does anyone do this, or is this really a non-concern?
All local tests have worked well. So I start a signoff thread now.
As a drop in replacement, man, apropros, and whatis seem to be working fine (at least after a DB generation). So you have my signoff for x86_64. -Dan
Am Wed, 18 Feb 2009 21:30:50 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
Holy smokes, did you try running the cron job? It generates an absurd amount of output, so for those people that get email when cron jobs produce output on stdout/stderr, this might be a bit much. Does anyone do this, or is this really a non-concern?
We can for sure run mandb --quiet in the cronjob. Debian does that. But then we will probably almost never get bugreports for broken pages. Depending on the settings what mails you want to get from cronjobs for stderr or stdout everybody could change that. I'm unsure what we should set as default. Other opinions? -Andy
On Wed, 2009-02-18 at 23:10 +0100, Andreas Radke wrote:
I've built man-db based on the package in community adding some changes I have found in a very good written page in the LFS book:
http://www.linuxfromscratch.org/lfs/view/6.4/chapter06/man-db.html
You can read there all about man page encoding and the expected locations and how to recode them. Therefor I have added the LFS recode script. This will allow us to recode broken man-pages when we will get bugreports. This should improve the current situation a lot.
Maybe we should write down later into the packager guide how to fix broken manpages, maybe even into the public wiki.
I didn't want to add a new system user "man" as the community package does. It seems to run fine without serious security concerns for me. If you think different feel free to drop a mail here.
It's not critical to create a database after installation. So I left out any install message. The cronjob will do this on its next run. You can surely run mandb manually to see how it goes.
All local tests have worked well. So I start a signoff thread now.
-Andy
Some notes about man-db.install: post_install/post_upgrade: chown -R man.users -> chown -R man:users. The . syntax is not POSIX compliant and I still have no idea why linux accepts this bullshit pre_remove that runs /bin/true: remove this function, it shouldn't be needed anymore with recent versions of pacman. An alternative to running /bin/true is just "return 0" instead btw. post_remove: you remove the man user, which leaves a /var/cache/man directory with files owned by an unknown user. This is a security bug, as the user is created with a >1000 userid also. When adding a new user afterwards, the user owns /var/cache/man. Either don't remove the user on post_remove, or delete /var/cache/man with it.
On Thu, Feb 19, 2009 at 2:36 AM, Jan de Groot <jan@jgc.homeip.net> wrote:
On Wed, 2009-02-18 at 23:10 +0100, Andreas Radke wrote:
I didn't want to add a new system user "man" as the community package does. It seems to run fine without serious security concerns for me. If you think different feel free to drop a mail here.
chown -R man.users -> chown -R man:users. The . syntax is not POSIX compliant and I still have no idea why linux accepts this bullshit
post_remove: you remove the man user, which leaves a /var/cache/man directory with files owned by an unknown user. This is a security bug, as the user is created with a >1000 userid also. When adding a new user afterwards, the user owns /var/cache/man. Either don't remove the user on post_remove, or delete /var/cache/man with it.
Don't Andy's and Jan's words here contradict with regard to creating a man user? -Dan
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
Don't Andy's and Jan's words here contradict with regard to creating a man user?
-Dan
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit. So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move. Anything else to improve? -Andy
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
Don't Andy's and Jan's words here contradict with regard to creating a man user?
-Dan
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit.
So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move.
Anything else to improve?
-Andy
I haven't tried the -2 pkg yet , but I noticed that with man-db I don't have coloured man pages anymore when using 'less' as the pager. To get coloured man pages, I need to use 'most' as pager. Is there anyone else who has this problem? It might be caused by a lack of a feature in man-db (I can't see why it would be the case) or a config issue. I haven't spent much time looking it up as it's a minor thing and works with 'most' although I would prefer 'less'. Eric
On Thu, Feb 19, 2009 at 9:13 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
Don't Andy's and Jan's words here contradict with regard to creating a man user?
-Dan
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit.
So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move.
Anything else to improve?
-Andy
I haven't tried the -2 pkg yet , but I noticed that with man-db I don't have coloured man pages anymore when using 'less' as the pager. To get coloured man pages, I need to use 'most' as pager. Is there anyone else who has this problem? It might be caused by a lack of a feature in man-db (I can't see why it would be the case) or a config issue. I haven't spent much time looking it up as it's a minor thing and works with 'most' although I would prefer 'less'.
Eric
http://bugs.archlinux.org/task/9130#comment31955 If man-db becomes the default man reader, should we use most as the default pager, or export GROFF_NO_SGR=1 by default?
On Thu, Feb 19, 2009 at 2:41 PM, Xavier <shiningxc@gmail.com> wrote:
On Thu, Feb 19, 2009 at 9:13 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
Don't Andy's and Jan's words here contradict with regard to creating a man user?
-Dan
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit.
So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move.
Anything else to improve?
-Andy
I haven't tried the -2 pkg yet , but I noticed that with man-db I don't have coloured man pages anymore when using 'less' as the pager. To get coloured man pages, I need to use 'most' as pager. Is there anyone else who has this problem? It might be caused by a lack of a feature in man-db (I can't see why it would be the case) or a config issue. I haven't spent much time looking it up as it's a minor thing and works with 'most' although I would prefer 'less'.
Eric
http://bugs.archlinux.org/task/9130#comment31955
If man-db becomes the default man reader, should we use most as the default pager, or export GROFF_NO_SGR=1 by default?
Can you find what this affects? Added a profile.d script to export this might not be a bad idea, but it's not exactly a good idea either. most as a default pager is probably not a good idea.
On Thu, Feb 19, 2009 at 3:58 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, Feb 19, 2009 at 2:41 PM, Xavier <shiningxc@gmail.com> wrote:
On Thu, Feb 19, 2009 at 9:13 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
Don't Andy's and Jan's words here contradict with regard to creating a man user?
-Dan
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit.
So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move.
Anything else to improve?
-Andy
I haven't tried the -2 pkg yet , but I noticed that with man-db I don't have coloured man pages anymore when using 'less' as the pager. To get coloured man pages, I need to use 'most' as pager. Is there anyone else who has this problem? It might be caused by a lack of a feature in man-db (I can't see why it would be the case) or a config issue. I haven't spent much time looking it up as it's a minor thing and works with 'most' although I would prefer 'less'.
Eric
http://bugs.archlinux.org/task/9130#comment31955
If man-db becomes the default man reader, should we use most as the default pager, or export GROFF_NO_SGR=1 by default?
Can you find what this affects? Added a profile.d script to export this might not be a bad idea, but it's not exactly a good idea either. most as a default pager is probably not a good idea.
I was thinking the same about using a profile script. Maybe that variable can be set in the config file: etc/man_db.conf
On Thu, Feb 19, 2009 at 3:05 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 3:58 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, Feb 19, 2009 at 2:41 PM, Xavier <shiningxc@gmail.com> wrote:
On Thu, Feb 19, 2009 at 9:13 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
Don't Andy's and Jan's words here contradict with regard to creating a man user?
-Dan
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit.
So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move.
Anything else to improve?
-Andy
I haven't tried the -2 pkg yet , but I noticed that with man-db I don't have coloured man pages anymore when using 'less' as the pager. To get coloured man pages, I need to use 'most' as pager. Is there anyone else who has this problem? It might be caused by a lack of a feature in man-db (I can't see why it would be the case) or a config issue. I haven't spent much time looking it up as it's a minor thing and works with 'most' although I would prefer 'less'.
Eric
http://bugs.archlinux.org/task/9130#comment31955
If man-db becomes the default man reader, should we use most as the default pager, or export GROFF_NO_SGR=1 by default?
Can you find what this affects? Added a profile.d script to export this might not be a bad idea, but it's not exactly a good idea either. most as a default pager is probably not a good idea.
I was thinking the same about using a profile script. Maybe that variable can be set in the config file: etc/man_db.conf
Adding -c to the TROFF and NROFF settings in man_db.conf fixes this
On Thu, Feb 19, 2009 at 3:11 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, Feb 19, 2009 at 3:05 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 3:58 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, Feb 19, 2009 at 2:41 PM, Xavier <shiningxc@gmail.com> wrote:
On Thu, Feb 19, 2009 at 9:13 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
> Don't Andy's and Jan's words here contradict with regard to creating > a man user? > > -Dan >
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit.
So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move.
Anything else to improve?
-Andy
I haven't tried the -2 pkg yet , but I noticed that with man-db I don't have coloured man pages anymore when using 'less' as the pager. To get coloured man pages, I need to use 'most' as pager. Is there anyone else who has this problem? It might be caused by a lack of a feature in man-db (I can't see why it would be the case) or a config issue. I haven't spent much time looking it up as it's a minor thing and works with 'most' although I would prefer 'less'.
Eric
http://bugs.archlinux.org/task/9130#comment31955
If man-db becomes the default man reader, should we use most as the default pager, or export GROFF_NO_SGR=1 by default?
Can you find what this affects? Added a profile.d script to export this might not be a bad idea, but it's not exactly a good idea either. most as a default pager is probably not a good idea.
I was thinking the same about using a profile script. Maybe that variable can be set in the config file: etc/man_db.conf
Adding -c to the TROFF and NROFF settings in man_db.conf fixes this
Hmmm do these settings look sane as default settings: DEFINE troff groff -mandoc -Tutf8 -c DEFINE nroff nroff -mandoc -Tutf8 -c We used to use -Tps (which seems silly from reading the groff man page) and the -c flags used to exist as well
Am Thu, 19 Feb 2009 15:11:02 -0600 schrieb Aaron Griffin <aaronmgriffin@gmail.com>:
On Thu, Feb 19, 2009 at 3:05 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 3:58 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, Feb 19, 2009 at 2:41 PM, Xavier <shiningxc@gmail.com> wrote:
On Thu, Feb 19, 2009 at 9:13 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
> Don't Andy's and Jan's words here contradict with regard to > creating a man user? > > -Dan >
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit.
So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move.
Anything else to improve?
-Andy
I haven't tried the -2 pkg yet , but I noticed that with man-db I don't have coloured man pages anymore when using 'less' as the pager. To get coloured man pages, I need to use 'most' as pager. Is there anyone else who has this problem? It might be caused by a lack of a feature in man-db (I can't see why it would be the case) or a config issue. I haven't spent much time looking it up as it's a minor thing and works with 'most' although I would prefer 'less'.
Eric
http://bugs.archlinux.org/task/9130#comment31955
If man-db becomes the default man reader, should we use most as the default pager, or export GROFF_NO_SGR=1 by default?
Can you find what this affects? Added a profile.d script to export this might not be a bad idea, but it's not exactly a good idea either. most as a default pager is probably not a good idea.
I was thinking the same about using a profile script. Maybe that variable can be set in the config file: etc/man_db.conf
Adding -c to the TROFF and NROFF settings in man_db.conf fixes this
I'd like to leave the package plain upstream. Maybe we can put this into a wiki page where we also write down how man-pages have to be encoded and where to put. -Andy
On Thu, Feb 19, 2009 at 3:15 PM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 15:11:02 -0600 schrieb Aaron Griffin <aaronmgriffin@gmail.com>:
On Thu, Feb 19, 2009 at 3:05 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 3:58 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, Feb 19, 2009 at 2:41 PM, Xavier <shiningxc@gmail.com> wrote:
On Thu, Feb 19, 2009 at 9:13 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote: > Am Thu, 19 Feb 2009 07:27:01 -0600 > schrieb Dan McGee <dpmcgee@gmail.com>: > >> Don't Andy's and Jan's words here contradict with regard to >> creating a man user? >> >> -Dan >> > > This was my mistake. I had cp'ed the install file from the > community pkg and missed make my changes before the commit. > > So a -2 pkg is now up for signoff. I removed the unwanted man > user creation. Added a msg for anybody upgrading from 2.5.3-1 > and earlier to remove the user and change permission on the db > dir. The cronjob runs in quiet mode now. Added a backup array > for its config file. Now it should be ready to move. > > Anything else to improve? > > -Andy >
I haven't tried the -2 pkg yet , but I noticed that with man-db I don't have coloured man pages anymore when using 'less' as the pager. To get coloured man pages, I need to use 'most' as pager. Is there anyone else who has this problem? It might be caused by a lack of a feature in man-db (I can't see why it would be the case) or a config issue. I haven't spent much time looking it up as it's a minor thing and works with 'most' although I would prefer 'less'.
Eric
http://bugs.archlinux.org/task/9130#comment31955
If man-db becomes the default man reader, should we use most as the default pager, or export GROFF_NO_SGR=1 by default?
Can you find what this affects? Added a profile.d script to export this might not be a bad idea, but it's not exactly a good idea either. most as a default pager is probably not a good idea.
I was thinking the same about using a profile script. Maybe that variable can be set in the config file: etc/man_db.conf
Adding -c to the TROFF and NROFF settings in man_db.conf fixes this
I'd like to leave the package plain upstream. Maybe we can put this into a wiki page where we also write down how man-pages have to be encoded and where to put.
Hmm, we ship modified config files for a lot of things (the "sane defaults" rationale). This one seems cryptic enough to boggle most people. It's not like there's a "turn_color_on = yes" setting... it's a command line arg to groff, which most people haven't heard of... to me it seems more beneficial to do it at the package level and we end up with groff output as close to what we got with the 'man' package as we can get. I'll log a bug with upstream for this one
On Thu, Feb 19, 2009 at 3:21 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, Feb 19, 2009 at 3:15 PM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 15:11:02 -0600 schrieb Aaron Griffin <aaronmgriffin@gmail.com>:
On Thu, Feb 19, 2009 at 3:05 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 3:58 PM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
On Thu, Feb 19, 2009 at 2:41 PM, Xavier <shiningxc@gmail.com> wrote:
On Thu, Feb 19, 2009 at 9:13 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote: > On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke > <a.radke@arcor.de> wrote: >> Am Thu, 19 Feb 2009 07:27:01 -0600 >> schrieb Dan McGee <dpmcgee@gmail.com>: >> >>> Don't Andy's and Jan's words here contradict with regard to >>> creating a man user? >>> >>> -Dan >>> >> >> This was my mistake. I had cp'ed the install file from the >> community pkg and missed make my changes before the commit. >> >> So a -2 pkg is now up for signoff. I removed the unwanted man >> user creation. Added a msg for anybody upgrading from 2.5.3-1 >> and earlier to remove the user and change permission on the db >> dir. The cronjob runs in quiet mode now. Added a backup array >> for its config file. Now it should be ready to move. >> >> Anything else to improve? >> >> -Andy >> > > I haven't tried the -2 pkg yet , but I noticed that with man-db I > don't have coloured man pages anymore when using 'less' as the > pager. To get coloured man pages, I need to use 'most' as pager. > Is there anyone else who has this problem? It might be caused by > a lack of a feature in man-db (I can't see why it would be the > case) or a config issue. I haven't spent much time looking it up > as it's a minor thing and works with 'most' although I would > prefer 'less'. > > Eric >
http://bugs.archlinux.org/task/9130#comment31955
If man-db becomes the default man reader, should we use most as the default pager, or export GROFF_NO_SGR=1 by default?
Can you find what this affects? Added a profile.d script to export this might not be a bad idea, but it's not exactly a good idea either. most as a default pager is probably not a good idea.
I was thinking the same about using a profile script. Maybe that variable can be set in the config file: etc/man_db.conf
Adding -c to the TROFF and NROFF settings in man_db.conf fixes this
I'd like to leave the package plain upstream. Maybe we can put this into a wiki page where we also write down how man-pages have to be encoded and where to put.
Hmm, we ship modified config files for a lot of things (the "sane defaults" rationale). This one seems cryptic enough to boggle most people. It's not like there's a "turn_color_on = yes" setting... it's a command line arg to groff, which most people haven't heard of... to me it seems more beneficial to do it at the package level and we end up with groff output as close to what we got with the 'man' package as we can get.
I'll log a bug with upstream for this one
Apparently Debian disables SGR output the same way we do some character translations in the groff package: The following is in /usr/share/groff/site-tmac/{man,mdoc}.local if n \{\ . \" Debian: Disable the use of SGR (ANSI colour) escape sequences by . \" grotty. . if '\V[GROFF_SGR]'' \ . output x X tty: sgr 0 .\} We could do the same, considering we already make additions to the tmac files - would anyone be against this?
On Thu, Feb 19, 2009 at 3:41 PM, Xavier <shiningxc@gmail.com> wrote:
On Thu, Feb 19, 2009 at 9:13 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
Don't Andy's and Jan's words here contradict with regard to creating a man user?
-Dan
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit.
So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move.
Anything else to improve?
-Andy
I haven't tried the -2 pkg yet , but I noticed that with man-db I don't have coloured man pages anymore when using 'less' as the pager. To get coloured man pages, I need to use 'most' as pager. Is there anyone else who has this problem? It might be caused by a lack of a feature in man-db (I can't see why it would be the case) or a config issue. I haven't spent much time looking it up as it's a minor thing and works with 'most' although I would prefer 'less'.
Eric
http://bugs.archlinux.org/task/9130#comment31955
If man-db becomes the default man reader, should we use most as the default pager, or export GROFF_NO_SGR=1 by default?
I would be better to export GROFF_NO_SGR=1 by default. 'most' is in extra so I guess we'll need to move it to core if it's the default pager. Most people probably use 'less' as we already have it in core.
On Thu, Feb 19, 2009 at 3:00 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 3:41 PM, Xavier <shiningxc@gmail.com> wrote:
On Thu, Feb 19, 2009 at 9:13 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
Don't Andy's and Jan's words here contradict with regard to creating a man user?
-Dan
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit.
So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move.
Anything else to improve?
-Andy
I haven't tried the -2 pkg yet , but I noticed that with man-db I don't have coloured man pages anymore when using 'less' as the pager. To get coloured man pages, I need to use 'most' as pager. Is there anyone else who has this problem? It might be caused by a lack of a feature in man-db (I can't see why it would be the case) or a config issue. I haven't spent much time looking it up as it's a minor thing and works with 'most' although I would prefer 'less'.
Eric
http://bugs.archlinux.org/task/9130#comment31955
If man-db becomes the default man reader, should we use most as the default pager, or export GROFF_NO_SGR=1 by default?
I would be better to export GROFF_NO_SGR=1 by default. 'most' is in extra so I guess we'll need to move it to core if it's the default pager. Most people probably use 'less' as we already have it in core.
Wait a tick.... Use the -c switch to revert to the old behaviour, printing a bold character c with the sequence `c BACKSPACE c' and an italic character c by the sequence `_ BACKSPACE c'. At the same time, color out-put output put is disabled. The same effect can be achieved by setting either the GROFF_NO_SGR environment variable or using the `sgr' X command (see below). GROFF_NO_SGR *disables* color output? Try unsetting all the less environment vars, maybe it does color on its own?
On Thu, Feb 19, 2009 at 10:57 AM, Andreas Radke <a.radke@arcor.de> wrote:
Am Thu, 19 Feb 2009 07:27:01 -0600 schrieb Dan McGee <dpmcgee@gmail.com>:
Don't Andy's and Jan's words here contradict with regard to creating a man user?
-Dan
This was my mistake. I had cp'ed the install file from the community pkg and missed make my changes before the commit.
So a -2 pkg is now up for signoff. I removed the unwanted man user creation. Added a msg for anybody upgrading from 2.5.3-1 and earlier to remove the user and change permission on the db dir. The cronjob runs in quiet mode now. Added a backup array for its config file. Now it should be ready to move.
Anything else to improve?
-Andy
There's a typo in the post-install message (required instead of requiered). I'm not a native speaker but I would change it to: echo "The system user \"man\" is not required anymore." echo "Please run \"userdel man\" and \"chown root:root /var/cache/man\""
participants (6)
-
Aaron Griffin
-
Andreas Radke
-
Dan McGee
-
Eric Bélanger
-
Jan de Groot
-
Xavier