-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
Le 24/07/2010 11:02, Osamu Aoki a écrit : > On Fri, Jul 23, 2010 at 10:14:10PM -0400, David Prévot wrote: >> Neither is /package/.info, and I'm sure many others. Giving an example >> for every one of them just to make sure that people who can't read the >> intro of a chapter would be able to understand any part of it is a >> non-issue in my point of view (anyway, it will make the document larger, >> and people would argue they /can't/ read it because it is too long ;-). > > Agreed but a generic short intro at the top of chapter may not be too bad. > > Just after <item>rename ... > > <item>copy template files such as <file><var>package</var>.install</file> > to something like <file><var>foo</var>.install</file> to match their > corresponding binary package names. Note that this list refers to the files that are created by dh_make, and those have actual names like <file>gentoo.install</file> (maybe keeping "gentoo" is fine here like in the other parts, if using "foo", here, you will need to define what it does mean ;-). So I guess it will be better to add this remark earlier: [...] Some of them come with filenames prefixed by the binary package name such as <tt><var>package</var></tt>. - -----+++++++++------- Those presented in this chapter prefixed by <tt><var>package</var></tt> which are not created by <prgn>dh_make</prgn> must of course be renamed to something like <file><var>foo</var>.install</file> to match their corresponding binary package names. - -----+++++++++------- Take a look at all of them. >> It needs to be reviewed because I'm not sure how of the way >> dh_installman(1) works, > > It relies on .TH line in the file to decide where it put man page these days. Sure (I've read the manpage ;-), but my concern is about the syntax of the file /package/.manpages: should the file be named with their path from the top level of the source code (the proposition here fits this comportment), or from the debian/ one, ore the debian/build/ one or even the debian/tmp/ one (ore looking in every one of them, in this order, I think I've read something like that a few time ago but can't remember right now)... > Yes. Starting sentence with "So ..." is my usual style. This > documentation uses a bit different style. I take your idea. > > I am thinking one of the following: > > option1: > | This is how <package>gentoo</package>'s <file>gentoo.manpages</file> file > looks > | like to install <file>doc/gentoo.1</file>: > > option2: > | To install <file>doc/gentoo.1</file> for the <package>gentoo</package> > | package as manpage, you create a <file>gentoo.manpages</file> file as: > > Both are followed by: > | <example> > | docs/gentoo.1 > | </example> The man page in gentoo source code is named exactly: <file>docs/gentoo.1x</file>, we may want to keep it that way (it is actually installed by dh_installdirs in gentoo's source code). For what is worth, I prefer your second option, but IMHO, make the intro as clear as possible is the best way to close this bug. Cheers David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkxLDLoACgkQ18/WetbTC/oScACfeiXq1kdYTEuLCR1lrjkfFhDv YQkAoIQiLJ7i2bkxqatFOUxOxLZe42h/ =0TbX -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
