[Bug 226488] Merge Review: texinfo

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Merge Review: texinfo


https://bugzilla.redhat.com/show_bug.cgi?id=226488





------- Additional Comments From pertusus at free.fr  2008-01-22 05:22 EST -------
(In reply to comment #7)

> I know PreReq is deprecated. IIRC Requires is practically PreReq without strict
> package order and since there is only one package in PreReq, Requires should do
> the same thing. Am I right?

I think that you are right in your recalling, but I don't think that
a Requires and a PreReq do the same in a transaction where more than
one package is involved. If one of the packages has a
Requires(post): /sbin/install-info
Then it may be possible that info is installed before bash, thus leading
to info post-scriptlets failing. So it seems that at least there should
be a
Requires(post): bash
But I am not sure that it will work with triggers. It seemsso,
however, since on
http://people.redhat.com/laroche/pyrpm/pyrpm-devel.html
this is explained, and it looks like post is done before the
triggers and so a Requires(post) is enough.

Additionnally, it looks like rpm adds automatically a /bin/sh
Requires(post), as can be seen in the rpmbuild output.
Requires(post): /bin/sh
So nothing should be needed.

I'll ask on the packaging list to be sure.


> > There is a build dependency loop texinfo -> ncurses-devel -> gpm-devel ->
> > install-info.
> >
>
> How do you suggest to change it?

I have no specific idea. I have noted it in the gpm merge review
if I recall well I suggested there to avoid depending on install-info.
I think that you should try coordinate with the ncurses/gpm maintainers.
(as a side note there is a weird ncurses-devel <-> gpm-devel cross
dependency, and also ncurse dlopens gpm, it is very strange but
unrelated).


-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.