Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 06 Aug 2012 08:34:02 +0100
From:      Matthew Seaman <>
To:        Matthias Petermann <>
Subject:   Re: Introducing new ports - best practises
Message-ID:  <>
In-Reply-To: <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 06/08/2012 08:10, Matthias Petermann wrote:

> at the moment I am working on porting the Tryton business solution
> and later GNU Health is planned.
> Tryton is made up of small modules (Python Eggs), each of them
> providing data models and business logic for a particular business
> domain - e.g. product management, invoicing, crm, sales... . The module=
> depend on each other in some ways.
> What is the proposed way to get this modules into the Ports
> Collection? Should I submit a PR for each single module or it is
> reasonable to create one PR for a bunch of new ports of the same
> category when they belong logically together?

First of all, this is prime material for the
list, where you'll get an audience of most of the people that work on
such things in FreeBSD.

I'd also like to point you at #bsdports on the EFNet IRC network: if you
want your work to be reviewed before you submit it, or are just looking
for some quick answers to any questions you may have, that's a good
place to ask.

To answer the question: historically the rule of thumb has been one PR
for each new port, and note in the body of the PR any dependencies on
other PRs.  Putting several ports into one PR is not a complete no-no,
but usually you'ld need some special justification.  Something like a
pair od ports with a master-slave relationship perhaps.



Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP:     Ramsgate
JID:               Kent, CT11 9PW

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla -



Want to link to this message? Use this URL: <>