Yeah, I might accept the "backwards compatibility with existing dependencies" argument, but I don't think it's something that's necessary for general use. In a post-split world, deb packages that use Twisted stuff will depend on specific twisted subproject packages. Anyway, I'm not the one doing the deb packages, but there are my two cents. On Sun, 6 Feb 2005 13:26:03 -0500, James Y Knight <foom@fuhm.net> wrote:
On Feb 6, 2005, at 6:41 AM, Christopher Armstrong wrote:
Yeah. "Twisted Core" is just used to disambiguate it from the other subprojects of Twisted. AIUI, "Twisted" is officially the networking framework. The tarball that contains everything will just be a convenience, and it will be called something like TwistedSumo.tar.bz2. I encourage packagers to name the twisted core package "twisted" and twisted subproject packages "twisted-foo". A "sumo" package is unnecessary on all non-barbaric packaging systems; I only think it's appropriate in tarball and win32 form.
I'm not sure that's right. I think it may be useful (and probably expected by users) on debian, say, to have a "twisted" package which installs every little bit of code associated with twisted, and a twisted-core package which is the core bits. The "twisted" package wouldn't actually contain any data, but simply depend on all the other packages. Such a package may actually even be *necessary*, in order to properly migrate dependancies forward (note that I'm not a debian packaging expert so I'm just guessing there).
James
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-- Twisted | Christopher Armstrong: International Man of Twistery Radix | -- http://radix.twistedmatrix.com | Release Manager, Twisted Project \\\V/// | -- http://twistedmatrix.com |o O| | Founding Member, Hobart Hacking Society w----v----w-+ -- http://hackingsociety.org/chapters/hash