How to build a BROKEN port?
m.seaman at infracaninophile.co.uk
Thu Dec 30 11:19:46 UTC 2010
On 30/12/2010 10:37, Da Rock wrote:
> On 12/30/10 20:12, Eitan Adler wrote:
>>>> Edit the port's Makefile and comment-out the BROKEN line.
>> Generally - don't do this.
> I kinda got that impression already, but can someone enlighten me why
> (apart from the obvious, of course- it could break the makefile if you
> forget)? And is that in general or just this line?
This advice is correct for someone who just wants to /use/ the ports --
not so good if your intention is to /develop/ the ports. And I think
fixing the reason a port is marked BROKEN certainly puts you in the
A very good tip: if you are editing the port, then it pays to check it
out from one of the anon-CVS servers while you work on it. You get all
the usual VCS capabilities and it's easier to revert any changes etc.
You don't need to check out the whole ports tree -- just your port of
interest will be fine, and you don't need to keep it in the normal ports
See Ion Mihai's article here for lots of good practices:
and all about FreeBSD Anon-CVS here:
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew at infracaninophile.co.uk Kent, CT11 9PW
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 267 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20101230/70814a62/signature.pgp
More information about the freebsd-questions