> On Sep 30, 2014, at 9:44 PM, Lawrence Velázquez <[email protected]> wrote: > > On Sep 30, 2014, at 10:09 PM, Ryan Schmidt <[email protected]> wrote: > >> On Sep 30, 2014, at 9:08 PM, Sean Farley wrote: >> >>> Ryan Schmidt writes: >>> >>>>> The question, to me, is: why is it still not >>>>> possible to distinguish foo+gcc and foo+clang in MacPorts? >>>> >>>> I'm not sure what you mean. >>> >>> Why can't all a port's variants be installed at the same time? >>> >>> $ port install boost >>> $ port install boost +gcc48 >>> >>> Every port could have its own custom prefix and only the active one >>> would be a symlink in /opt/local. >> >> That's not what variants are for. That's what subports are for. > > Subports don't install files differently from regular ports, though.
That is correct. > Sean's proposal (as I understand it) is more or less how Homebrew installs > things. You'd end up with something like this: > > /opt/local/ > ├── bin/ > │ └── foo -> ../dports/foo+bar/bin/foo > ├── etc/ > ├── lib/ > │ └── libfoo.dylib -> ../dports/foo+bar/lib/libfoo.dylib > ├── dports/ > │ ├── foo+bar/ > │ │ ├── bin/ > │ │ │ └── foo > │ │ ├── etc/ > │ │ ├── lib/ > │ │ │ └── libfoo.dylib > │ │ ├── share/ > │ │ └── var/ > │ └── foo+baz/ > │ ├── bin/ > │ │ └── foo > │ ├── etc/ > │ ├── lib/ > │ │ └── libfoo.dylib > │ ├── share/ > │ └── var/ > ├── share/ > └── var/ > > MacPorts keeps simultaneously-installed (but not active) ports in archives; > Homebrew keeps them in subdirectories. I understand the proposal, but I don't agree that we should implement it. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
