This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [ITP] Questions


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim O'Callaghan wrote:
> Hi,
> 
> Sorry about the delay with getting back to this stuff.
> 
> I'd like to ask a few quick questions before i send my formal ITP's
> 1) should i send a separate ITP email for each one or one for all of them?

Choose based on whether it makes sense for them to be discussed as a
unit, or not. If packages are entirely unrelated, use separate emails.
Combine multiple packages into a single ITP mail if it makes little
sense for one to be added to the Cygwin distro without the other.


> 2) bundling - If i need to include a new tool/lib to support a particular feature
>    such as String::ShellQuote or CVSps, should i bundle it in or separate it out?
>     are there guidelines?

Separate packages are nicer, because then you can update the tool/lib
without updating the 'parent' package, and vice versa. Plus, there's
always the possibility another package might want to depend on the
tool/lib later.

> 3) If a package needs a specific tool to build it, such as asciidoc being needed for 
>    git documentation, does it also need to be supported or not? if so does it need
>    to be bundled with the source, or as a separate package?

It really ought to be possible to rebuild any Cygwin package using only
software available as Cygwin packages, so a package would be preferable.
Separately - the answer to 2) applies equally here too.


Max.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)

iD8DBQFDfdN5fFNSmcDyxYARAg29AJ9XtPak16gfcQ20lOhjFL/MhuECEwCgrKXA
KArsHvi7oenlEqx8k4UC9go=
=Syzp
-----END PGP SIGNATURE-----


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]