On Fri, Mar 10, 2006 at 05:07:44PM +0100, Kees Zeelenberg wrote:
> 1) The time needed for production of a patched package is usually not very 
> large for packages with require the autotools to build. For other packages, 
> more time may be needed.

Did your create any documentation about that? I mean, the exact commands
you used to create the various binary packages, including the used
./configure options, etc.

> The limiting factor, however, is not the time to 
> build, but the time available to the developers, which at present is not 
> very large; see the decrease in the frequency of updates at 
> http://gnuwin32.sourceforge.net/ and 
> http://gnuwin32.sourceforge.net/oldnews.html during the last year.

How do you people organize it?
Were are your standards / guidelines?
Where do the source files come from, which way are they repacked
(to ...-src.zip) and built?

> So, when 
> a  considerable number of packages will have to be rebuild, this may take a 
> long time-span.

I didn't say anthing like that. I just wante to give some compatibility
patches to you. This doesn't affect binary packages at all! Just your
source packages would need to be "rebuild".

> 2) New packages are quickest imported when they are in the form of a 
> Gnuwin32 package, i.e. with subdirectories bin, doc, include, lib, man, and 
> so on.

I don't understand. What you describe are binary packages. Shouldn't
you more interested in source packages and building scripts?

What exactly to you need? What do you build automatically?

In other words: What do the different Gnuwin32 developer provide?
What is done automatically? Which roles do what tasks?

Without knowing *how* the team works, I don't know how to support it.


Greets,

    Volker

-- 
Volker Grabsch
---<<(())>>---
Administrator
NotJustHosting GbR


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
GnuWin32-Users mailing list
GnuWin32-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnuwin32-users

Reply via email to