Selecting at least one option out of multiple groups
Elizabeth Myers
elizabeth at interlinked.me
Sun Feb 1 10:43:32 UTC 2015
On 02/01/15 00:55, Scot Hetzel wrote:
> On Wed, Jan 28, 2015 at 3:31 AM, Elizabeth Myers
> <elizabeth at interlinked.me> wrote:
>> Hello,
>>
>> I am porting a piece of software (purple-plugin-pack) to FreeBSD. It
>> contains numerous plugins for Pidgin all under one pack (over 50). They
>
> Is this going to be one port that installs over 50 plugins (based on
> what is selected), or is it going to be over 50+1 ports?
I was thinking one port, since they come as a pack, and the idea of
adding over 50 ports to the tree is... well, that's 50 ports I'd have to
submit. That's quite an undertaking.
> +1 port (pidgin-purple-plugin-pack) [meta-port (see x11/kde4 for an example)]
> - allows you to select which purple plugins to install (depends on
> selected pidgin-purple-plugin-* ports)
If there's a meta port, I guess it wouldn't matter if no plugins were
selected by it? I still think it'd be ideal to categorise them in the
meta port, at least by protocol/general use.
> over 50 ports
> - individual port for each plugin (i.e.
> graphics/pidgin-purple-plugin-album
> net-im/pidgin-purple-plugin-autoprofile
> net-im/pidgin-purple-plugin-autoreply
> net-im/pidgin-purple-plugin-awaynotify
> shells/pidgin-purple-plugin-bash
> ...)
> - allows individual plugins to be installed/de-installed without
> having to re-install the purple-plugin-pack
This is definitely appealing, I will admit.
> If you go the over 50+1 ports route, each port could have it's own
> option settings.
So far none of the plugins in the pack have their own option settings,
as far as I can tell. This does leave open the possibility, though.
--
Cheers,
Elizabeth Myers
More information about the freebsd-ports
mailing list