version 1.39, 2001/11/12 21:01:28 |
version 1.40, 2001/12/19 21:33:48 |
|
|
<br> |
<br> |
|
|
<ul><li> |
<ul><li> |
Create the directories <code>files, patches, pkg</code>. |
Create the directories <code>patches, pkg</code>. |
<li> |
<li> |
Create these empty files <code>pkg/DESCR, pkg/PLIST</code> |
Create these empty files <code>pkg/DESCR, pkg/PLIST</code> |
</ul> |
</ul> |
|
|
MASTER_SITE_SUBDIR in your Makefile. |
MASTER_SITE_SUBDIR in your Makefile. |
<li> |
<li> |
Ports normally correspond to given versions of software. Once they are retrieved, files are checksummed and compared to the recorded |
Ports normally correspond to given versions of software. Once they are retrieved, files are checksummed and compared to the recorded |
checksum in files/md5. So, to avoid confusion, DISTFILES and PATCHFILES should have clearly visible version numbers: |
checksum(s) in distinfo. So, to avoid confusion, DISTFILES and PATCHFILES should have clearly visible version numbers: |
don't retrieve foo-latest.tar.gz if it is a link to foo-1.0.5.tar.gz. If necessary, gently ask the original program author |
don't retrieve foo-latest.tar.gz if it is a link to foo-1.0.5.tar.gz. If necessary, gently ask the original program author |
to make such distinctions clear. |
to make such distinctions clear. |
<li> |
<li> |
|
|
</ul> |
</ul> |
|
|
<br><li> |
<br><li> |
Create a checksum in <i>files/md5</i> by typing <b>make makesum</b>. |
Create a checksum in <i>distinfo</i> by typing <b>make makesum</b>. |
Then verify the checksum is correct by typing <b>make checksum</b> |
Then verify the checksum is correct by typing <b>make checksum</b> |
<ul><li> |
<ul><li> |
In some rare cases, files checksums can't be verified reliably. By all means, porters should try to find sites that are reliable. Communicating |
In some rare cases, files checksums can't be verified reliably. By all means, porters should try to find sites that are reliable. Communicating |
|
|
<ul><li> |
<ul><li> |
You can add a port configuration script named `configure' to a directory |
You can add a port configuration script named `configure' to a directory |
named <code>scripts/</code>. This will be run before any configuration |
named <code>scripts/</code>. This will be run before any configuration |
specified by GNU_CONFIGURE or HAS_CONFIGURE is run. |
specified by CONFIGURE_STYLE is run. |
<li> |
<li> |
If GNU_CONFIGURE is used you may want to run ./configure --help |
If GNU configure is used you may want to run ./configure --help |
to see what options are available. |
to see what options are available. |
<li> |
<li> |
Anything that you may want to override can be changed by adding the |
Anything that you may want to override can be changed by adding the |
|
|
<li> |
<li> |
Only patch one source file per patchfile, please, |
Only patch one source file per patchfile, please, |
<li> |
<li> |
Use <b>diff -p -u</b> to generate patches, |
Use <b>make update-patches</b> to generate patches, |
<li> |
<li> |
All patches MUST be relative to ${WRKDIST}, |
All patches MUST be relative to ${WRKDIST}, |
<li> |
<li> |
|
|
Try setting <code>SEPARATE_BUILD</code><br> |
Try setting <code>SEPARATE_BUILD</code><br> |
<ul><li> |
<ul><li> |
If the port can build with object files outside its source tree, |
If the port can build with object files outside its source tree, |
this is cleaner (many programs using <code>GNU_CONFIGURE</code> can), |
this is cleaner (many programs using <code>CONFIGURE_STYLE=gnu</code> can), |
and may help people who mount their ports tree on several arches. |
and may help people who mount their ports tree on several arches. |
<li> |
<li> |
This can also spare you some effort, as you will possibly be able to |
This can also spare you some effort, as you will possibly be able to |
|
|
<i>/etc</i> or <i>/etc/<name></i> only if the files do not exist. |
<i>/etc</i> or <i>/etc/<name></i> only if the files do not exist. |
If the files exist, display a message that says such-and-such files need |
If the files exist, display a message that says such-and-such files need |
to be modified. This also guarantees that the files will be included in |
to be modified. This also guarantees that the files will be included in |
the package since everything under <i>/usr/local</i> is included in the PLIST |
the package since everything under <i>/usr/local</i> is included in the PLIST. |
|
After a package has been installed the contents of <code>pkg/MESSAGE</code> |
|
will be displayed if it exists. |
|
|
<p> |
<p> |
The OpenBSD file locations are: |
The OpenBSD file locations are: |