On Apr 12, 2016, at 2:52 PM, Christopher Jones <jon...@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? How do users know what functionality they have installed when they install ROOT6 from source? How do users add additional functionality that wasn't built when they first built ROOT6? [the answer is probably 'rebuild'] -- Daniel J. Luke _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
