Re: overwriting files from modules packages

2003-09-01 Thread Bob Proulx
martin f krafft wrote: > also sprach Bob Proulx <[EMAIL PROTECTED]> [2003.09.01.0853 +0200]: > > Abbreviated example: > > make-pkg --append-to-version -2-686-smp kernel_modules > > Produces: > > /usr/share/man/man4/bcm5700-2-4-21-2-686-smp.4.gz > > Not by default. I could make that happen manu

Re: overwriting files from modules packages

2003-09-01 Thread martin f krafft
also sprach Bob Proulx <[EMAIL PROTECTED]> [2003.09.01.0853 +0200]: > Abbreviated example: > > make-pkg --append-to-version -2-686-smp kernel_modules > > Produces: > > /usr/share/man/man4/bcm5700-2-4-21-2-686-smp.4.gz Not by default. I could make that happen manually though, which is what I

Re: overwriting files from modules packages

2003-09-01 Thread Bob Proulx
martin f krafft wrote: > I am the (new) maintainer of bcm5700-source, a modules package for > the broadcom gigabit adapter. The final package, > bcm5700-module-${KVERS}, includes a manpage, > /usr/share/man/man4/bcm5700.4.gz. I just now ran into the problem > that while installing the 2.4.22 image

Re: overwriting files from modules packages

2003-08-31 Thread Martin Schulze
Matt Zimmerman wrote: > On Sun, Aug 31, 2003 at 12:18:26AM +0200, martin f krafft wrote: > > > also sprach Matt Zimmerman <[EMAIL PROTECTED]> [2003.08.31.0013 +0200]: > > > If you want two different versions of documentation, they need to > > > be named differently. Alternatively, you can just sp

Re: overwriting files from modules packages

2003-08-30 Thread Junichi Uekawa
> Which is what I will do, probably. It's just annoying... but > a statement in README.Debian will do... update-alternatives is usually used in managing multiple manpages. I don't know if it's a overkill, but it's somewhat friendlier than documenting in README.Debian. regards, junich

Re: overwriting files from modules packages

2003-08-30 Thread martin f krafft
also sprach Matt Zimmerman <[EMAIL PROTECTED]> [2003.08.31.0130 +0200]: > > I don't think a single manpage warrants another binary package. So > > the only real solution is to put the manpage into > > /usr/share/doc//docs ... > > Or name it -.. Which is what I will do, probably. It's just annoyin

Re: overwriting files from modules packages

2003-08-30 Thread Matt Zimmerman
On Sun, Aug 31, 2003 at 12:18:26AM +0200, martin f krafft wrote: > also sprach Matt Zimmerman <[EMAIL PROTECTED]> [2003.08.31.0013 +0200]: > > If you want two different versions of documentation, they need to > > be named differently. Alternatively, you can just split the > > documentation into a

Re: overwriting files from modules packages

2003-08-30 Thread martin f krafft
also sprach Matt Zimmerman <[EMAIL PROTECTED]> [2003.08.31.0013 +0200]: > If you want two different versions of documentation, they need to > be named differently. Alternatively, you can just split the > documentation into a separate package and allow only one version > to be installed at once. I

Re: overwriting files from modules packages

2003-08-30 Thread Matt Zimmerman
On Sat, Aug 30, 2003 at 11:05:40PM +0200, martin f krafft wrote: > I am the (new) maintainer of bcm5700-source, a modules package for the > broadcom gigabit adapter. The final package, bcm5700-module-${KVERS}, > includes a manpage, /usr/share/man/man4/bcm5700.4.gz. I just now ran into > the proble

overwriting files from modules packages

2003-08-30 Thread martin f krafft
I am the (new) maintainer of bcm5700-source, a modules package for the broadcom gigabit adapter. The final package, bcm5700-module-${KVERS}, includes a manpage, /usr/share/man/man4/bcm5700.4.gz. I just now ran into the problem that while installing the 2.4.22 image and modules, the bcm5700-modules-