[ archivemail-Bugs-1574720 ] packaging request

[SourceForge.net <no...@so...>]

Bugs item #1574720, was opened at 2006-10-10 20:37
Message generated for change (Comment added) made by nikosch
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1574720&group_id=49630

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 7
Private: No
Submitted By: g2boojum (g2boojum)
Assigned to: Nikolaus Schulz (nikosch)
Summary: packaging request

Initial Comment:
I'm in the process of packaging 0.6.2 for Gentoo, and
I've come across a couple of things that make packaging
a bit of a pain for us.  The first is that "python
setup.py build" doesn't work out-of-the-box, because
the tarball contains archivemail.py. and not
archivemail.  The second is that "python setup.py
install" fails because "archivemail.1" isn't present in
the archive.  It's possible to generate it using "make
archivemail.1", but then our users need to have
docbook2X installed as a build dependency, and it's
pretty heavy.  Would it be possible to have the
setup.py script updated to use "archivemail.py" instead
of "archivemail" by default, and an already-generated
"archivemail.1" file included in the tarball for the
next release, please?

----------------------------------------------------------------------

>Comment By: Nikolaus Schulz (nikosch)
Date: 2006-11-03 04:11

Message:
Logged In: YES 
user_id=1594781

This is fixed in archivemail 0.7.0, which was released today. 
Thanks for reporting!

----------------------------------------------------------------------

Comment By: Peter Poeml (poeml)
Date: 2006-10-13 14:55

Message:
Logged In: YES 
user_id=78531

In my package (SUSE ;) I don't see any breakage with the latest tarball. I use:

sed -i 's,man/man1,share/man/man1,' setup.py
%{__python} setup.py build

to build, and 

%{__python} setup.py install --prefix=%{_prefix} --root %{buildroot}
ln -s archivemail.py %{buildroot}/%{_bindir}/archivemail

to install.

If there was previously a file "archivemail" in the tarball, sorry, I have no idea 
why and how it was created.

What's odd about a *.py python script? :-)

I actually used this Makefile (uncommitted change) to create the tarball:

Index: Makefile
===============================================
====================
--- Makefile    (revision 115)
+++ Makefile    (working copy)
@@ -31,8 +31,13 @@
        cvs tag -F current
        cvs tag -F $(VERSION_TAG)
 
+tarball:
+       svn export https://svn.sourceforge.net/svnroot/archivemail/trunk 
archivemail-$(VERSION)
+       tar czf $(TARFILE) archivemail-$(VERSION)
+       rm -r archivemail-$(VERSION)
+
 upload:
-       (cd dist && lftp -c 'open upload.sf.net && cd incoming && put $
(TARFILE)')
+       (lftp -c 'open upload.sf.net && cd incoming && put $(TARFILE)')

With a 'cp' or 'mv', applied to the archivemail directory before tar'ing it up, the 
archivemail script could be created. 

About the man page: I didn't know how to generate it. All those docbook util 
cruft
is a mystery to me. (On some machines I may have the right tools
installed by accident, but that's about it.)

----------------------------------------------------------------------

Comment By: Nikolaus Schulz (nikosch)
Date: 2006-10-12 04:26

Message:
Logged In: YES 
user_id=1594781

Thanks for your report. 

You are right, the last released tarball looks odd. A new
release is pending anyway, I'll take care that this is fixed. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=456910&aid=1574720&group_id=49630