libgcc update ... to 4.9?

["René J.V. Bertin"]

Hi,

On Aug 21, 2014, at 12:17, Clemens Lang wrote:

>> I think my macports.conf file fulfils those conditions, but just in case you
>> forgot something, I've attached it.
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: main.log.bz2
Type: application/x-bzip2
Size: 21202 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-users/attachments/20140822/5331270e/attachment.bz2>
-------------- next part --------------



> I couldn't see anything that would prevent the use of binary archives. Can you
> attach the main.log of an attempt to install a package that should use binary
> archives, but didn't?

I still had the log from the attempt to install libgcc 4.9; it's attached.

> You should enable the sandbox again, since the problem has been fixed.

Ok.

> Note that setting macportsuser to the name of your account defeats the
> purpose of the user. Using a separate unprivileged user here makes sure no
> build system can modify (or even read) your files. Your configuration is
> insecure and should be avoided.

Surely, but how many such build systems does MacPorts carry?. And in a sense I want the build system to be able to read my files. I no longer run `port install` as myself because too many ports need actual root privileges during install, but for the rest I like to have the build tree to be mine. For a number of ports (like kdelibs4), the work source directory is actually a symlink to a directory in one of my own working directories. Takes a bit of discipline (to avoid reverting my changes to stock) but it greatly increases turn-over once you master it. For cmake projects, I can simply do a make in the lowest build directory holding my changes that has a CMakeLists.txt, and then do a `make install/fast` from there to install the new files directly into ${prefix}.

(I'm much more concerned about what could happen during an install, and not so much to my files but to system files. Which is why my whole /usr/local tree is owned by me and not by root, and why I ran `port install` as myself for so long.)

R.