jonesc at hep.phy.cam.ac.uk
Tue Apr 12 12:04:21 PDT 2016
> On 12 Apr 2016, at 7:56 pm, Daniel J. Luke <dluke at geeklair.net> wrote:
> On Apr 12, 2016, at 2:52 PM, Christopher Jones <jonesc at hep.phy.cam.ac.uk> wrote:
>>>> Some of them create additional libraries for the new features, some just add the functionality to existing ones. Most will also extend the introspection system as part of root. None can be built as afterthoughts. You have to configure ROOT from the start with the features you want. So for this port there is no chance in hell I am going to implement them as sub-ports.
>>> It would be nice if upstream could be convinced to 'fix' this.
>> You’ll need to convince them (and me) first its a bug that needs fixing. I don’t see it that way.
> How do other package managers (that don't have variants) deal with ROOT6?
I guess they have to decide a set of options that most people want, and just go with that.
> How do users know what functionality they have installed when they install ROOT6 from source?
If they are installing from source they are expected to know what they are doing, and therefore pick the options they need. They are reasonably well documented.
> How do users add additional functionality that wasn't built when they first built ROOT6? [the answer is probably 'rebuild’]
you can’t. Reinstall with the new options.
None of the above changes my opinion on what Macports should do.
> Daniel J. Luke
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1910 bytes
Desc: not available
More information about the macports-dev