[Bug 225301] Merge Review: automake17

bugzilla at redhat.com bugzilla at redhat.com
Wed Sep 19 13:51:06 UTC 2007


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: automake17


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





------- Additional Comments From pertusus at free.fr  2007-09-19 09:51 EST -------
(In reply to comment #13)
> a conflict makes sure that you can install automake-1.7 when automake17 is
> installed. AFAIK rpm currently allows this.

Indeed (although in that case there will certainly be a file 
conflict). But since it is obsoleted this is not useful since
the  automake-1.7 will be removed in normal cases. Conflicts
should be avoided, but I won't make it a blocker. However,
it shouldn't conflict with anything else than 1.7*.

> I'd rather not go the road with the multiple obsoletes. I think using < 1.8
> is as simple and clear as rpm currently allows. 
> If someone uses an ancient automake version, I'm quite sure he/she knows how to
> install it. 

But it renders the Obsoletes of 1.6 by 16 unusefull. And are
you sure that the right version gets installed when there are
multiple Obsoletes? It is not that clear. Obsoleting only 1.7.9 
is clearer as it means that it simply was a rename. And your
argument holds if there is only 
Obsoletes: 1.7.9
If someone uses an ancient automake version, I'm quite sure he/she
knows how to install it.

> This doesn't concern users of FC-2 and newer as they already have automake17 and

I don't think that we should target some users, but try to do
as right as possible for those who have old automake versions 
installed, whatever version it is. In any case, this is not very 
important since the users who want to do such upgrades and keep
compat packages are likely to be knowledgable, but in any case we
should do the best we can.


-- 
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.




More information about the package-review mailing list