[flub: Re: [Visualpython-users] packaging issues/bugs]

[Floris B. <fb...@so...>]

Oops, discovered I didn't do a list reply here... sorry

----- Forwarded message from flub -----

> To: Jonathan Brandmeyer <jbr...@ea...>
> Subject: Re: [Visualpython-users] packaging issues/bugs
> User-Agent: Mutt/1.5.6+20040722i
> Date: Wed, 8 Dec 2004 12:15:26 +0000
> 
> On Mon, Dec 06, 2004 at 11:04:46PM -0500, Jonathan Brandmeyer wrote:
> > I noticed that you are not an official Debian Developer (according to
> > people.debian.org).  Out of curiosity, is this packaging effort part of
> > an application to become one?
> 
> I am indeed not.  Initially I just wanted a nice package on my own
> system for VPython.  But I might consider applying for DD and maintain
> python-visual officially if I think I can commit the time for it.
> I'll see how it goes.
> 
> Floris
> 
> -- 
> Debian GNU/Linux -- The power of freedom
> www.debian.org | www.gnu.org | www.kernel.org
> 
> rs mailing list
> Vis...@li...
> https://lists.sourceforge.net/lists/listinfo/visualpython-users
> Status: RO
> X-Status: A
> Content-Length: 1764
> Lines: 44
> 
> .1 required=5.0 tests=AWL,BAYES_00,
> 	RCVD_NUMERIC_HELO,TO_ADDRESS_EQ_REAL autolearn=no version=2.64
> Status: O
> Content-Length: 1764
> Lines: 44
> 
> On Mon, 2004-12-06 at 19:49 +0000, Floris Bruynooghe wrote:
> > Not sure if this is the right place for this really, this is a -users
> > list after all...
> > 
> > Anyway:
> > I've been playing around a bit with the package and ran accros the
> > following issues wich would be nice to see fixed.
> 
> I'll look into these issues when I get a chance.  I am in the middle of
> semester exams, and won't be able to set aside some time for this until
> next week.
> 
> 
> > This is fairly clear.  Why is cvisual not using a Makefile.am?  If you
> > could wirite a Makefile.am this would be solved automatically.
> 
> Because Automake and libtool wants to force me into a model of building
> libraries that is flat wrong for i386-pc-mingw32 and
> powerpc-apple-darwin*.  Since it only worked properly for one out of the
> three platforms that VPython is directly supported on, I chose to write
> my own single Makefile.in rather than maintain three (or even just two)
> separate build procedures.
> 
> All of the issues that you mentioned are straightforward to fix, and I
> will be happy to do so.  If you want to submit a patch, I would be
> grateful.
> 
> I noticed that you are not an official Debian Developer (according to
> people.debian.org).  Out of curiosity, is this packaging effort part of
> an application to become one?
> 
> -Jonathan
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> ___________________________________________
----- End forwarded message -----

-- 
Debian GNU/Linux -- The power of freedom
www.debian.org | www.gnu.org | www.kernel.org