Re: Packaging for Cheeseshop and Debian
On Thu, 15 Mar 2007, Josselin Mouette wrote: > Le mercredi 14 mars 2007 à 09:48 +0100, Raphael Hertzog a écrit : > > > I have some idea about doing each of those, but no real clues about > > > packaging for both Python's Cheeseshop and a Debian package > > > simultaneously. Where should I start learning about the issues and > > > recommendations? > > > > http://wiki.debian.org/DebianPythonFAQ > > > > Check the part concerning eegs. > > Wow, just another place with completely outdated (to the point I don't > think it has ever been accurate) documentation about python packaging, > especially python-support. The egg part is still OK, but indeed the rest was rather outdated. Thanks for fixing it (even if it looks like empty now :-)). Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packaging for Cheeseshop and Debian
Le mercredi 14 mars 2007 à 09:48 +0100, Raphael Hertzog a écrit : > > I have some idea about doing each of those, but no real clues about > > packaging for both Python's Cheeseshop and a Debian package > > simultaneously. Where should I start learning about the issues and > > recommendations? > > http://wiki.debian.org/DebianPythonFAQ > > Check the part concerning eegs. Wow, just another place with completely outdated (to the point I don't think it has ever been accurate) documentation about python packaging, especially python-support. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Re: Packaging for Cheeseshop and Debian
Raphael Hertzog <[EMAIL PROTECTED]> writes: > On Thu, 15 Mar 2007, Ben Finney wrote: > A module that uses "eggs" to load another module is certainly > egg-ready itself. However if the dependency isn't egg-ready, then > the package expecting an egg of its dependency will be broken unless > we add the egg support to its dependency. > > > What would need to be done upstream for this criterion to change? > > Switch from distutils to setuptools as shown with the example patch. Thanks, this is clear. -- \ "Teach a man to make fire, and he will be warm for a day. Set a | `\ man on fire, and he will be warm for the rest of his life." -- | _o__) John A. Hrastar | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packaging for Cheeseshop and Debian
Hi, On Thu, 15 Mar 2007, Ben Finney wrote: > > Check the part concerning eegs. > > The page says: > > Adding "egg support" is only required in some specific cases: when > another software uses the python module via an egg and when this > egg support is not yet integrated upstream." > > What is meant by "this egg support is not yet integrated upstream"? You have two ways to install python modules: - the traditional distutils - the eggs-powered setuptools > Does this refer to the "upstream" of the package which depends, or the > packages upon which it depends, or both? The latter. A module that uses "eggs" to load another module is certainly egg-ready itself. However if the dependency isn't egg-ready, then the package expecting an egg of its dependency will be broken unless we add the egg support to its dependency. > What would need to be done upstream for this criterion to change? Switch from distutils to setuptools as shown with the example patch. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packaging for Cheeseshop and Debian
[Please follow http://www.debian.org/MailingLists/#codeofconduct>; I don't ask for copies of list messages to be sent to me, so by default please don't.] Raphael Hertzog <[EMAIL PROTECTED]> writes: > On Wed, 14 Mar 2007, Ben Finney wrote: > > I have some idea about [Debia packages and Python eggs], but no > > real clues about packaging for both Python's Cheeseshop and a > > Debian package simultaneously. Where should I start learning about > > the issues and recommendations? > > http://wiki.debian.org/DebianPythonFAQ Thanks, that whole page is a good start. I'll consult it often. > Check the part concerning eegs. The page says: Adding "egg support" is only required in some specific cases: when another software uses the python module via an egg and when this egg support is not yet integrated upstream." What is meant by "this egg support is not yet integrated upstream"? Does this refer to the "upstream" of the package which depends, or the packages upon which it depends, or both? What would need to be done upstream for this criterion to change? -- \ "I bought some powdered water, but I don't know what to add." | `\ -- Steven Wright | _o__) | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packaging for Cheeseshop and Debian
Hi, On Wed, 14 Mar 2007, Ben Finney wrote: > Howdy all, > > I'm writing an application[0] in Python, and am nearly at the point > where I want to package it. I need to do so in a way that's useful to > me, so that means a Debian package; and useful to anyone using Python, > so that means a Python egg available in the Cheeseshop. > > I have some idea about doing each of those, but no real clues about > packaging for both Python's Cheeseshop and a Debian package > simultaneously. Where should I start learning about the issues and > recommendations? http://wiki.debian.org/DebianPythonFAQ Check the part concerning eegs. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Packaging for Cheeseshop and Debian
Howdy all, I'm writing an application[0] in Python, and am nearly at the point where I want to package it. I need to do so in a way that's useful to me, so that means a Debian package; and useful to anyone using Python, so that means a Python egg available in the Cheeseshop. I have some idea about doing each of those, but no real clues about packaging for both Python's Cheeseshop and a Debian package simultaneously. Where should I start learning about the issues and recommendations? I'd also like to discuss strategies for adding both Debian and Python packaging information when keeping the source in a version-control system, but that should probably be a separate thread. [0]: a small HTTP-accessible helper application -- \ "I was stopped by the police for speeding; they said 'Don't you | `\ know the speed limit is 55 miles an hour?' I said 'Yeah I know, | _o__) but I wasn't going to be out that long.'" -- Steven Wright | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
