[Bug 216106] Review Request: python-twisted-words - Twisted Words contains Instant Messaging implementations

[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: Review Request: python-twisted-words - Twisted Words contains Instant Messaging implementations


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


kevin at tummy.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|163778                      |163779
              nThis|                            |




------- Additional Comments From kevin at tummy.com  2006-12-28 13:33 EST -------
>I can only parrot what the Twisted developers say, and they say this is indeed
>the intention for a reasonably long series of Twisted (e.g. the 2.x series)
>
>If they actually live up to this or will fix stuff when something goes wrong is
>something I cannot predict of course.

Thats fine... as long as they plan to keep compatibility thats good. 

>
>What I am reasonably (99.9%) sure of is that *if* there are any problems of
>that kind an updated -core will be put out to fix whatever is wrong.

Well, if that has to happen, you will also have to add a versioned requirement
to any of the subpackages that need the new fixed core package. 
Otherwise you can have a case where someone installs fc6, installs
python-twisted-core, and then many months later installs say
python-twisted-words. Since there isn't a version requirement there it will
happily install with the older python-twisted-core package. 

>
>I don't think versioned depends make a lot of sense in this scenario since you
>cannot predict when it will *stop* working, so you cannot put an upper limit on
>your versioned depends anyway.  Whatever you put in is going to break >regardless .

As long as the subpackages are working with the available core package there
shouldn't be an issue. If there is something in a subpackage that needs a fix in
the core package, I think at that point you will have to add a versioned
requirement for the fixed core. 

So, I think there is no issue now with it being unversioned. 
If it needs to be versioned later for a fix you can do so at that point. 

I see no further blockers here... this package is APPROVED. 

Please remember to close this package review as NEXTRELEASE once it's been
imported and built. 

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