-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sounds good to me!
Bye,
Max
Am 21.04.2011 um 18:16 schrieb Alexander Hansen:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Here's draft 2.
>
>
> 3.7 Source Policy
>
> Sources should normally be downloaded from the location(s) that the
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here's draft 2.
3.7 Source Policy
Sources should normally be downloaded from the location(s) that the
upstream developer(s) use, and any modifications for Fink should be done
through the use of a PatchFile and/or a PatchScript. Do not make changes
m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/20/11 4:15 PM, Daniel Macks wrote:
> Yup. If anyone disputes the "supply source + patches rather than patched
> sources", it's a formal requirment of many standard licenses.
> Might want to tweak "Upload the tarball to a site where fink can
> down
Yup. If anyone disputes the "supply source + patches rather than
patched sources", it's a formal requirment of many standard licenses.
Might want to tweak "Upload the tarball to a site where fink can
download it." statement to clarify that it's a *public* site for other
users (or their finks)
Sounds good to me.
-- Dave
On Apr 20, 2011, at 12:16 PM, Alexander Hansen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> 3.7 Source Policy
>
> Sources should normally be downloaded from the location(s) that the
> upstream developer(s) use, and any modifications for Fink should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
3.7 Source Policy
Sources should normally be downloaded from the location(s) that the
upstream developer(s) use, and any modifications for Fink should be done
through the use of a PatchFile and/or a PatchScript. Do not make changes
manually and use a
