Re: Python .egg support in Debian

2005-11-29 Thread Thomas Viehmann
Bob Tanner wrote:
> Is there an agreement amongst the interested debian-python
> developers/packagers that Debian must support .egg's?
Well, let's agree that this is desirable, perhaps strongly, depending on
how widespread the use of .eggs is, to support applications using it.

> Answering the -IF- will let us move forward to the HOW. 
Likely the IF is connected to the HOW: The number of Debian python
people objecting to zipped .egg files seems to be far larger than those
not willing to support some form of "unpacked eggs".

Kind regards

T.

-- 
Thomas Viehmann, http://thomas.viehmann.net/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Python .egg support in Debian

2005-11-28 Thread Martin v. Löwis

Bob Tanner wrote:

Is there an agreement amongst the interested debian-python
developers/packagers that Debian must support .egg's?

Answering the -IF- will let us move forward to the HOW. 


Terminology is really critical here. Eggs are a certain structure
of information: a meta-data system along with library routines
and command line utilities to access them. I agree Debian
should support them.

.eggs are a specific distribution format for Eggs: zipfiles
with included meta-data. Terminology is unclear here: it
*also* is another distribution format: directory ending
in .egg, with the metadata as files inside the directory.
I do *not* agree that Debian should support those.

There is yet another form distribution format for Eggs:
egg-infos. This is what I think Debian should support.

Regards,
Martin


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Python .egg support in Debian

2005-11-28 Thread Bob Tanner
On Monday 28 November 2005 03:22 pm, Josselin Mouette wrote:
> You are completely misunderstanding the issue. There can be no such
> thing as "Debian support for eggs". There can only be some Debian
> packages of eggified software. And there will be, as some developers
> will want to make them.

Verbage, I'll change mine to be "Debian packages of eggified software". 

> The problem is that eggs are broken by design, and we're trying to
> convince upstream to fix their flaws, not only for our benefit but for
> that of all distributions.

Water under the bridge and it doesn't really matter. 

Upstream's design =might= be fatally flawed and you can argue this point for 
months and upstream will never change (ie Mozilla anyone?).

Let's move past it. Deal with the technical issues and create the policies, 
framework, and potential tools used to make "Debian packages of eggified 
software". 

> As they don't seem to listen to any of the arguments that were showed,
> we'll obviously have to use crude hacks to get these applications in
> Debian. The only remaining question may be which hack is the less ugly.

Stop swinging the Josselin-clue-by-four at upstream and turn all the energy 
into debian-python :-) 

Is easy-deb the less ugly of the hacks?
-- 
Bob Tanner <[EMAIL PROTECTED]>  | Phone : (952)943-8700
http://www.real-time.com, Minnesota, Linux | Fax   : (952)943-8500
Key fingerprint = AB15 0BDF BCDE 4369 5B42  1973 7CF1 A709 2CC1 B288


pgp2wdsJjIou5.pgp
Description: PGP signature


Re: Python .egg support in Debian

2005-11-28 Thread Martin Skøtt
On Mon, Nov 28, 2005 at 01:51:26PM -0600, Bob Tanner wrote:
> Starting a separate thread from the "formencode as .egg in Debian ??"
> discussion since this issue is internal to Debian and I don't want DD's to
> "beat-up" upstream development anymore. :-)

Thank you for bringing this up. The beating of welcoming upstream
developers is quite embarrising to follow.

> Is there an agreement amongst the interested debian-python
> developers/packagers that Debian must support .egg's?

As a long time Python developer and Debian user i fint it absolutely
necessary for Debian to have some kind of support for .eggs's.

Python developers has benefitted of the quality of Debian for a long
time and it would be sad to see it not continue because of
disagreement about .egg's.
-- 
Regards,
Martin Skøtt
Pragmatic Python developer


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Python .egg support in Debian

2005-11-28 Thread Josselin Mouette
Le lundi 28 novembre 2005 à 13:51 -0600, Bob Tanner a écrit :
> IF Debian decides -not- to support .egg's a few python code bases (modules,
> applications, etc) will break. 
> 
> Looking into the future more python code bases will move to .egg so the
> number of broken code bases will only increase.
> 
> I want to state what I think is the obvious, Debian must support .egg's.
> 
> NOTE: The implementation of how .egg's are supported can be left to another
> thread.

You are completely misunderstanding the issue. There can be no such
thing as "Debian support for eggs". There can only be some Debian
packages of eggified software. And there will be, as some developers
will want to make them.

The problem is that eggs are broken by design, and we're trying to
convince upstream to fix their flaws, not only for our benefit but for
that of all distributions.

As they don't seem to listen to any of the arguments that were showed,
we'll obviously have to use crude hacks to get these applications in
Debian. The only remaining question may be which hack is the less ugly.

Regards,
-- 
 .''`.   Josselin Mouette/\./\
: :' :   [EMAIL PROTECTED]
`. `'[EMAIL PROTECTED]
  `-  Debian GNU/Linux -- The power of freedom


signature.asc
Description: Ceci est une partie de message	numériquement signée


Python .egg support in Debian

2005-11-28 Thread Bob Tanner
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Starting a separate thread from the "formencode as .egg in Debian ??"
discussion since this issue is internal to Debian and I don't want DD's to
"beat-up" upstream development anymore. :-)

Good or bad python .egg's are here to stay. Following the "formencode
as .egg in Debian ??" thread I understand the following.

IF Debian decides -not- to support .egg's a few python code bases (modules,
applications, etc) will break. 

Looking into the future more python code bases will move to .egg so the
number of broken code bases will only increase.

I want to state what I think is the obvious, Debian must support .egg's.

NOTE: The implementation of how .egg's are supported can be left to another
thread.

Is there an agreement amongst the interested debian-python
developers/packagers that Debian must support .egg's?

Answering the -IF- will let us move forward to the HOW. 

- -- 
Bob Tanner <[EMAIL PROTECTED]>  | Phone : (952)943-8700
http://www.real-time.com, Minnesota, Linux | Fax   : (952)943-8500
Key fingerprint = AB15 0BDF BCDE 4369 5B42  1973 7CF1 A709 2CC1 B288
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDi1++fPGnCSzBsogRAjI+AJwIQbPm5GWBYSGve4Rfly6nH2FmzACgw1Aa
KojmA4grMV/vAyNfDr8qR20=
=9tD4
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]