Re: Hypothetical pkg-python alioth project

2006-03-27 Thread Gustavo Franco 

Paul Wise wrote:

On Tue, 2006-03-28 at 01:16 +0200, Carlos Galisteo wrote:
(...)

 Anyone knowing about this project status?


We have some packages in SVN[1] (and one package in debian). Only a few
people involved[2]. We have yet to do a proper website[3], announcement
and callout.
(...)


python-modules is "on hold" for me, because i need some time to finnish 
our policy[0] discussing it with the current members. If somebody 
maintaining python modules wants to join the team and help with the 
documentation tell me then i'll reorganize this project in my own TODO,

preparing a useful website and doing an announcement.

Btw, i'm more active in pkg-ltsp and pkg-gnome atm. I was planning to do
some debtags and python-modules work in May.

[0] = 
http://svn.debian.org/wsvn/python-modules/www/python-modules-policy.rst?op=file&rev=0&sc=0


Thanks,
Gustavo Franco <[EMAIL PROTECTED]>


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

Re: Hypothetical pkg-python alioth project (was:Re: .egg in Debian summary?)

2006-03-27 Thread Paul Wise 
On Tue, 2006-03-28 at 01:16 +0200, Carlos Galisteo wrote:

>  IMHO that would be a great way to mantain python modules, and also a
> good "place" for more inexperienced people (like me) to be useful by
> doing delegated stuff and learning from the inside.
> 
>  Wait...It seems there already exists a "Python Modules Packaging
> Team" project [1] in Alioth:

Correct. We use #debian-python (oftc) and the python-modules-team list
on alioth.

>  Anyone knowing about this project status?

We have some packages in SVN[1] (and one package in debian). Only a few
people involved[2]. We have yet to do a proper website[3], announcement
and callout.

 1. http://svn.debian.org/wsvn/python-modules/
 2. 
http://svn.debian.org/wsvn/python-modules/metainfo/python-modules.team?op=file&rev=0&sc=0
 3. 
http://svn.debian.org/wsvn/python-modules/www/python-modules-policy.rst?op=file&rev=0&sc=0

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Hypothetical pkg-python alioth project (was:Re: .egg in Debian summary?)

2006-03-27 Thread Carlos Galisteo 
On Mon, 27 Mar 2006 22:24:39 +0200, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> BTW, wouldn't it be time to create a pkg-python alioth project much like
> the pkg-perl one to globally co-maintain all the python modules ?

 IMHO that would be a great way to mantain python modules, and also a good 
"place" for more inexperienced people (like me) to be useful by doing delegated 
stuff and learning from the inside.

 Wait...It seems there already exists a "Python Modules Packaging Team" project 
[1] in Alioth:
 
 Registered: 2005-06-29 15:17
 Activity Percentile: 0%

 Anyone knowing about this project status?



[1]http://alioth.debian.org/projects/python-modules/

--- 
Carlos Galisteo  
Jabber_Id::cgalisteo en jabber.org 
PGP_key::http://k-rolus.net/~cgalisteo/cgalisteo.gpg 
Key_Fingerprint::F888 6FBA 9145 B5A2 C187  66D6 5B8C 027A 69AD BE65 
--- 


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

Re: .egg in Debian summary?

2006-03-27 Thread Raphael Hertzog 
On Mon, 27 Mar 2006, Brian Sutherland wrote:
> > > > 
[...]
> > My opinion is that we probably shouldn't distribute eggs but we must make
> > it possible for our users to use them. So I think that the egg meta-info
> > ought to be distributed either within a package directly (when the content
> > of the egg matches the content of a single package) or as separate
> > meta-packages depending on the various packages.
> > 
> > From what I understood this is solution 3 above.
> 
> For what it's worth, I will be converting most of my packages that build
> with setuptools to use option 3.
> 
> That is, of course, until there is some kind of consenus/decision.

If you have done that, can you post your patch to the list ? I have never
packaged Python related stuff yet, but I recently made a patch to update
the kid package (#359012) and tried to look quickly what would be needed
to achieve that but each time I ended with a .egg in the .deb ...

So it would be great to have a example of how this ought to be done.

BTW, wouldn't it be time to create a pkg-python alioth project much like
the pkg-perl one to globally co-maintain all the python modules ?

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: .egg in Debian summary?

2006-03-27 Thread Brian Sutherland 
On Sat, Mar 25, 2006 at 04:09:52PM +0100, Raphael Hertzog wrote:
> > > 3. Using Phillip's .egg-info solution
> > > 
> 
> Well, since there's no progress, it's up to you as package maintainer to
> take the decision. The day when we have a real policy here, it will still
> be time to change things.
> 
> My opinion is that we probably shouldn't distribute eggs but we must make
> it possible for our users to use them. So I think that the egg meta-info
> ought to be distributed either within a package directly (when the content
> of the egg matches the content of a single package) or as separate
> meta-packages depending on the various packages.
> 
> From what I understood this is solution 3 above.

For what it's worth, I will be converting most of my packages that build
with setuptools to use option 3.

That is, of course, until there is some kind of consenus/decision.

-- 
Brian Sutherland

Metropolis - "it's the first movie with a robot. And she's a woman.
  And she's EVIL!!"


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