[Bug 175438] Review Request: smart -- Next generation package handling tool

bugzilla at redhat.com bugzilla at redhat.com
Fri Jan 27 11:53:31 UTC 2006


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

Summary: Review Request: smart -- Next generation package handling tool


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





------- Additional Comments From jarkko at saunalahti.fi  2006-01-27 06:53 EST -------
>> - Shouldn't smart-usermode obsolete smart-update and not ksmarttray? I  
>> might be wrong but if you just read the decriptions you get that impression.  
  
> Other ksmarttray packages are linked against smart-update, so doing what you  
> suggest could cause conflicts. Obsoleting it in ksmarttray doesn't have that  
> problem.

Are linked against? Do you mean that other ksmarttray packages require
smart-update? In that case I don't understand your reasoning because I think
smart-usermode replaces smart-update in this spec. (And doesn't replacing mean
obsoleting?)

If you mean other ksmarttray packages provide smart-update, you forget that they
also provide ksmarttray. Obsoleting smart-update in smart-usermode doesn't mean
ksmarttray would be removed if the user has ksmarttray installed. Our ksmarttay
will replace the old ksmarttray.

The only situation I can think of where this would actually cause conflicts
would be a one where the user tries to take ksmarttray and
smart-update/smart-usermode from different repositories. And even then the
conflict would happen only if the user would try to take the same version of
those packages from different repositories.

Even if such a conflict would happen you forget that fedora-extras doesn't (and
shouldn't) have to support third party repositories like that. The third parties
should remove smart from their repos when fedora-extras starts providing it.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the fedora-extras-list mailing list