-----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
manually and use a changed source archive as a Source in your Fink
packaging.

If a VCS checkout (e.g. from git or svn) is to be used, e.g. because a
project doesn't do formal releases, or a fix for a particular issue has
been added between releases of a package, an acceptable source can be
generated via the following method:
1. Check out the package, preferably at a definite revision of the VCS.
Make an archive from the VCS checkout (e.g. zip, tar, tar.gz, or tar.bz2).
2. Give the tarball a unique version. For example, you can include the
VCS revision in the archive name, e.g. foo-0svn1234.tar.gz for a package
that doesn't make releases, or bar-1.2.3+svn4567.tar.bz2 for a Fink
package which is between upstream releases.
3. Use the same Version in your .info file.
4. It is also useful to put the commands that you ran to generate the
source tarball in the DescPackaging field.

Upload the tarball to a public download site where users can use fink to
download it. If you don't have ready access to one, ask on the Fink
developers mailing list or the #fink IRC channel, and someone should be
able to help.



3.8 File Download Policy

Packages are not to download any files during the unpack, patch,
compile, install, or build phases of the build process. Any large
patches (i.e. larger than can be accommodated conveniently in a
PatchFile) that need to be applied should set up as additional Sources
in accordance with the Source Policy.

Packages may download data in a PostInstScript after they have been
installed on the system, under some limited circumstances:

* No updates to the package itself are allowed.
* The nature of the data is such that it couldn't easily be packaged for
Fink. E.g. virus definitions for clamav can be downloaded during this
phase, because they change continually.
When in doubt, contact the Fink Core Team.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2wWGAACgkQB8UpO3rKjQ+twwCaAg24jC0CUoTpx8oISuOVPy+s
LGMAnR8y4Wn/9dZtLhVzMePjJWdfm5mr
=M2NM
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to