zip file with updated Solaris and HP-UX packagers.
Replaces 415226, 415227, 415228.

Changes made to take advantage of new PEP241 changes in
the Distribution class.

Logged In: YES 
user_id=21627

Which of the three attached files is the right one (19633,
19634, or 19635)? Unless they are all needed, we should
delete the extra copies.

I recommend to apply PEP 2 to this patch: A library PEP is
needed (which could be quite short), documentation, perhaps
test cases. Most importantly, there must be an identified
maintainer of these modules. Are you willing to act as the
maintainer?

Logged In: YES 
user_id=12810

Any of the three (they're all the same). SourceForge
hiccuped during the upload, and I don't have permission to
delete the duplicates.

I don't exactly understand what you mean by applying PEP 2.
I uploaded this per Marc Lemburg's request for the latest
versions of patches 41522[6-8]. He's acting as as the
integrator in this case (see
http://mail.python.org/pipermail/distutils-sig/2001-December/002659.html).
I let him know about the duplicate uploads, so hopefully
he'll correct it. If you can and want, feel free to delete
the 2 of your choice.

I agree they need to be documented. As soon as I can, I'll
submit changes to the Distutils documentation.

Finally, yes, I'll act as maintainer. I'm on the
Distutils-sig and as soon as some other poor soul who has to
deal with Solaris or HP-UX tries them, I'm there to work out
issues.

Logged In: YES 
user_id=21627

You volunteering as the maintainer is part of the
prerequisites of accepting new modules, when following PEP
2, see

http://python.sourceforge.net/peps/pep-0002.html

It says: "developers ... will first form a group of
maintainers. Then, this group shall produce a PEP called a
library PEP."

So existance of a PEP describing these library extensions
would be a prerequisite for accepting them. If MAL wants to
waive this requirement, it would be fine with me. However,
such a PEP could also share text with the documentation, so
it might not be wasted effort.

Logged In: YES 
user_id=12810

OK, the PEP seems to me to mean most of this is done.

These additions are not library modules, they are Distutils
"commands". So the way i read it, the Distutils-SIG (where
I've been hanging around for some time) are the Maintainers.

The documentation will be 2 new chapters for the Distutils
manual "Creating Solaris packages" and "Creating HP-UX
packages" each looking a whole lot like "Creating RPM packages".

Does that clarify anything, or am I still missing a clue?

p.s. Thanks for cleaning up the extra uploads!

Logged In: YES 
user_id=38388

Mark, could you reupload the ZIP file ? I cannot download it
from the SF page (the file is mostly empty).

Also, is the documentation already included in the ZIP file ?
If not, it would be nice if you could add them as well.

I don't require a special PEP for these changes, BTW, but
I do require you to maintain them.

Thanks.

Logged In: YES 
user_id=12810

New file submitted. No documentation yet, but I am committed
to maintaining them.

Logged In: YES 
user_id=38388

I will try to checkin your latest version into CVS today. The PSF will
still require you to sign a contributor agreement for these
addition, though, after these have been through the legal
review phase.

http://www.python.org/psf/psf-contributor-agreement.html

Is that acceptable ?

Note: I'm still awaiting the documentation for these files.

Thanks.

Logged In: YES 
user_id=38388

Mark, I checked in your code, but still need the 
documentation to not get beaten over the head
by Fred ;-)

TIA.

Logged In: YES 
user_id=21627

Given the recent discussion, I think we consider this patch 
withdrawn for the moment. If there is any change to its 
status, please submit a new patch.