Jack Howarth wrote:
Martin,
So what is the recommended method for resolving conflicts over
manpages if update-alternatives is the wrong approach?
Personally, I would rename one of them. I would rather not to find a man
page than be shown one with the right name that is not the one I am
On 17 Apr 2010, at 09:04, Martin Costabel wrote:
Jack Howarth wrote:
Martin,
So what is the recommended method for resolving conflicts over
manpages if update-alternatives is the wrong approach?
Personally, I would rename one of them. I would rather not to find a
man
page than be
Jack Howarth wrote:
In order to work around the conflicts over ffi.3,
ffi_call.3 and ffi_prep_cif.3 between the libffi and
gcc45 package, I am looking at adding the calls to
update-alternatives to gcc45. Looking at the openmotif4.info
as an example, I see...
PostInstScript:
Martin,
So what is the recommended method for resolving conflicts over
manpages if update-alternatives is the wrong approach?
Jack
ps Regarding my leaving the update-alternatives in the info file,
I didn't remove it because my approach was not to randomly
prune things from the info
In order to work around the conflicts over ffi.3,
ffi_call.3 and ffi_prep_cif.3 between the libffi and
gcc45 package, I am looking at adding the calls to
update-alternatives to gcc45. Looking at the openmotif4.info
as an example, I see...
PostInstScript:
update-alternatives --install
