From: Matthew Seaman on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/06/2010 12:36:33, RW wrote:
> On Mon, 07 Jun 2010 18:04:37 +0100
> Matthew Seaman <m.seaman(a)infracaninophile.co.uk> wrote:
>
>> On 07/06/2010 17:34:39, RW wrote:
>>> If it's a metaport then it does have an origin.
>>
>> It certainly needs an origin if some other port is going to depend on
>> it. Which is usually the case for metaports, but not necessarily so.
>
> A metaport is a port and has an origin by definition. What you are
> referring to is a metapackage.

Right. So the 'meta' nature is irrelevant, and you might as well say if
it's a port, then it has an origin: otherwise, it's a package. That
makes sense. Quite a lot of sense really, although I think most people
don't think quite so precisely about such things.

Cheers,

Matthew

- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew(a)infracaninophile.co.uk Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwONL4ACgkQ8Mjk52CukIxZyACdEcA7IIy1zm5IPAV/RpbCLsFj
V2UAn2KJXIZSlsZ73tDzfKIQknocLXFd
=ef8h
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Matthew Seaman on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/06/2010 08:53:53, Matthew Seaman wrote:
> So, you're creating your own meta-port that exists only to be depended
> on by the ports you specifically want to have installed? That's a
> really good idea. You might need to fill out the contents of your
> "wanted-ports" meta-port a bit more, but the concept seems sound to me.

Actually, I thought this was a good enough idea that I had a go at
implementing it. My first cut at doing this is available at:

http://www.infracaninophile.co.uk/wanted-ports.shar

What do people think? Unless this meets with utter horror or there are
some horrendous bugs, I'll tidy it up, add a man page and submit it as a
new port in a week or so.

Cheers,

Matthew

- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew(a)infracaninophile.co.uk Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwORVYACgkQ8Mjk52CukIzwegCaAhV/gRXkKLkjD7627SrkJGho
hJ0AnjNI9kVYN8h4xVgg9gtq9XO+JeRT
=lygQ
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= on
On Mon, 07.06.2010 at 01:53:32 +0200, Thomas Rasmussen wrote:
> Hello,
>
> I've been wondering about something: When I write a script or webapp that
> needs some port to run, like a perl module, I install the needed port and
> life is good (tm). A year later when I've completely forgotten about the
> script I go do some spring-cleaning of the ports on the server, and I see
> some perl module that doesn't have any dependencies, and delete it. Fast
> forward a few days when I discover the script doesn't work anymore, cue
> face-palm, remove bullet from foot, etc.

Been there, done that. Apart from all that has already been suggested,
you might want to take a look at pkg_cutleaves. You can make an exclude
list of ports you don't want to have removed, other than that, it really
helps when doing the spring cleaning :)

Regards,
Uli
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"