Port system "problems"

[Matthew Seaman]

On 26/06/2012 19:46, Marcus von Appen wrote:
> I can't see that from the rough outline given earlier. What I understood
> is that some stagedir is used to build mono, then packages (-lib, -doc,
> -whatever) are created and installed.
> If you do not use downloaded packages, but install them yourself, you'd
> need to rebuild the complete mono port on an update.
> 
> Happy to be corrected here

I don't know anything about the particulars of the mono port, but if it
makes sense to divide it into several slave ports, then that will still
be possible.  Use of sub-ports is not going to be mandatory.  Well,
possibly with the exception of docs and/or examples, but that shouldn't
be a huge burden for anyone.

Remember what the big win is here: a binary package system that is fit
for purpose and that preserves as much of the functionality and
flexibility of the ports as possible.  Yes, compiling from source
yourself is the gold standard, but we think it would be pretty great if
there was a binary package management system that was good enough that
you don't actually /have/ to do that if you don't want to.

Yes, it's complicated, but the ports is already hideously complicated,
and I don't think this is that much worse: just moving the complication
around a bit.

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
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...
Name: signature.asc
Type: application/pgp-signature
Size: 267 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20120626/c4d16f89/signature.pgp