On Mar 19, 2013, at 19:18, Lawrence Velázquez lar...@macports.org wrote:
On Mar 16, 2013, at 5:45 PM, Jeremy Huddleston Sequoia jerem...@apple.com
wrote:
I think I mentioned in the past that globbing would be nice to add to the
portgroup. That way, you could blacklist *gcc-4.2 ...
On 2013-03-20 14:30, Leo Singer wrote:
Are changes like this to port1.0/ reflected by 'sudo port selfupdate'?
Changes to base/ first require a new release of MacPorts itself and then
they will be available with a selfupdate.
Also note that there are different branches. At the moment,
On Mar 20, 2013, at 09:21, Rainer Müller wrote:
On 2013-03-20 14:30, Leo Singer wrote:
Are changes like this to port1.0/ reflected by 'sudo port selfupdate'?
Changes to base/ first require a new release of MacPorts itself and then
they will be available with a selfupdate.
Right. So test
On Mar 16, 2013, at 5:45 PM, Jeremy Huddleston Sequoia jerem...@apple.com
wrote:
I think I mentioned in the past that globbing would be nice to add to the
portgroup. That way, you could blacklist *gcc-4.2 ...
https://trac.macports.org/changeset/104174
Testing welcome. Encouraged, even.
Hello,
I need to blacklist all versions of gcc 4.4. I don't think that Apple ever
shipped GCC 4.4 with Xcode, so I think that the only compiler I really have to
worry about is 'macports-gcc-4.4'. However, let's say that I wanted to
blacklist all flavors of gcc 4.2. Is that what 'gcc-4.2' would
No, blacklisting gcc-4.2 will just blacklist gcc-4.2
I think I mentioned in the past that globbing would be nice to add to the
portgroup. That way, you could blacklist *gcc-4.2 ...
--Jeremy
On Mar 16, 2013, at 14:35, Leo Singer aron...@macports.org wrote:
Hello,
I need to blacklist all
On Mar 16, 2013, at 5:35 PM, Leo Singer aron...@macports.org wrote:
I need to blacklist all versions of gcc 4.4. I don't think that Apple ever
shipped GCC 4.4 with Xcode, so I think that the only compiler I really have
to worry about is 'macports-gcc-4.4'. However, let's say that I wanted to
