Re: man page symlinks on symlinked binary

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Lamont Peterson escribió:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 19 Sep 2007 21:44:16 +0300
Ville Skyttä <ville.skytta@xxxxxx> wrote:

On Wednesday 19 September 2007, Martin Marques wrote:

The thing is that the discussion started flipping towards why, if
there is a binary symlink, there isn't a man page symlink? This
could, in the case of cdrecord and wodim, or mkisofs and genisofs,
end in bugtrack tickets for those packages, but I am more
interested in a general solution, for all packages that have binary
symlinks.

So, shouldn't there be something in respect of this issue in the
packaging policy?
I support that (or the more or less AFAIK equivalent 'echo ".so
man1/wodim.1"
cdrecord.1' approach as an alternative to symlinks).  Could you
write a
draft for that?  I can take it onwards from there in the packaging
committee.

I would suggest creating a cdrecord(1) man page that says "This is no more.  See wodim(1), which replaces it."  Put that cdrecord(1) man page into the wodim package.  This way, we teach people that there's been a change and we don't get "Um, when I type 'man cdrecord' I get a man page for something totally different; what gives?" kinds of questions/bug reports/requests.

If they read the man they would note that:

NOTE
There  may  be  similarities  and  differences between this program and
other disk recording application(s). See the CREDITS and  AUTHORS  sec-
tions below to learn about the origin of wodim.


And later that:

This application is a spinoff  from  the  original  program  "cdrecord"
delivered  in  the cdrtools package [1] created by Joerg Schilling, who
deserves the most credits for its success. However, he is not  involved
into the development of this spinoff and therefore he shall not be made
responsible for any problem caused by it. Do not refer to this applica-
tion  as  "cdrecord", do not try to get support for wodim by contacting
the original authors.

So, better would be to teach users to read the manual.

This is obviously IMHO.


- -- Lamont Peterson <lamont@xxxxxxxxxxxx>
Senior Instructor
Guru Labs, L.C. [ http://www.GuruLabs.com/ ]

NOTE:  All messages from this email address should be digitally signed with my
       0xDC0DD409 GPG key. It is available on the pgp.mit.edu keyserver as
       well as other keyservers that sync with MIT's.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFG8Xon+YBsl9wN1AkRAhdtAJ43J8X8zY++WFz3J/yP2rp5zNhcUwCgpbtn
YHhhBo5yl29FWGpPCR8RDTc=
=KqqQ
-----END PGP SIGNATURE-----


--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux