On Sun, Mar 12, 2006 at 06:52:59PM +0100, Kees Zeelenberg wrote:
> It's simple and easy: just put the package in the form bin / include / lib
> / ... / src (derived from DJGPP, http://www.delorie.com/djgpp/). For
> auto-packages, this can be done by a "make install" in a separate
> directory. The zip package and the setup program are then created by shell
> scripts.
Thanks for your reply, but I'm still unsure whether I got you right.
Maybe it's just a little detail I didn't understand yet.
If I got it right, I'll send one big package (e.g. TarGZ or ZIP file)
to you, containing sources, binaries, docs, etc.
This package will never directly be available for download.
Instead, you'll split that package into smaller ZIP packages and
create the two self-installing packages.
Did I unterstand you correctly?
If I did:
What kind of package do you prefer? (ZIP? TarGZ? TarBZ2?)
Should I send it to you via email, or should I upload it
to my server and send a link to you?
(Please don't answer that anything of that is okay. I'd like to
know the variants you *prefer*.)
How and in what format do the other developers contribute
their code to you?
Why isn't that procedure explained in something like
"GnuWin32 maintainer docs"? I'm sure it's a FAQ ...
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
