portfile
submissions
maintainer
DarwinPorts submissions
Submitting a Port
Using a standardised approach to submitting the Portfiles and
associated patches scripts, etc allows us to keep track of port
submissions, process them efficiently and get them submitted as
quickly as possible to our dports CVS tree. The following sections
will describe the standard port submission procedures.
Where to submit
All ports should be submitted via the DarwinPorts
bugzilla tool
. Your submission will be automatically emailled to the
members of the
darwinports-bugs mailing list. If you are uncertain about
any aspect of your port, you may also want to email it with your
questions and the bug number to
DarwinPorts
mailing list.
If you are submitting a modification, or an update to an
existing port, please assign the port to the current maintainer
in your bugzilla submission, so that the automatic email is
directed to the maintainer, who will be best suited to deal
with your submission.
Updates and modifications should be submitted as diffs. See
updating a port below
Using bugzilla to submit a Port
The following section describes in some more detail how to
use Bugzilla to submit your port.
Submission parameters
Project:
Make sure you select the DarwinPorts
project.
Component:
Select "dports" as the component.
Assigned to:
Please assign UPDATEs and COMMENTs on
existing ports to the maintainer. Otherwise, if
this is a NEW port or an RFC, please leave
blank.
URL:
You may use this field to point to the
portfile if it is available online, or to point
to the homepage of the program project.
Summary:
The summary field should one of a number
of standardised elements,
NEW: portname-1.2.3
Please use this format for
the submission of new ports.
UPDATE portname-1.2.3
Please use this format for
the submission of updates to ports.
Please use diffs!
REVISION: portname-1.2.3
Please use this format for the
submission of changes to a current,
uncommitted port submission
RFC: portname-1.2.3
Please use this format for
the submission of Request for
Comments on a Portfile.
ATTACHMENT: portname-1.2.3
to add an attachment you
will have use the query tool.
Once you have selected the correct
port, please use this format in the
summary field for your
submission.
Description:
The description field should contain the
following information as per the example given
here here.
Final comments on Port submission
The following general points should also be borne in
mind when submitting to bugzilla:
Small changes or portfiles should be
inlined.
Larger changes should be attached as a
single file, tar works wonderfully for this.
Multiple patched files should be bundled
together using tar and attached to the submission
Currently attachments must be sent in
using the current bug number, remeber to query
bugzilla to find out the current bug number, select
that bug and use the 'Create a New Attachment'
link.
Updating a port
The following guidelines are for submitting updates to
ports that are currently in the tree
All updates and modifications to existing ports should
be sent in as diffs.
There are a couple of ways to obtain correct diff
formats
Using diff:
Obtain the original file (oldfile)
cp oldfile oldfile.new
edit oldfile.new and save your changes
diff -u oldfile oldfile.new > oldfile.diff
Use bugzilla to submit your port UDPATE
Or using cvs diff:
checkout the original source using cvs
edit the files and save your changes
cvs diff -u sourcefile > sourcefile.diff
use bugzilla to submit your port UPDATE
Lastly, if your update consists of several files, use tar
to bundle them into one file for submission