Inconsistent criteria of success on the buildbot
Hi, A while ago I committed a new subport for geant4.10.2 which is currently broken (in the meantime I lacked time/motivation to look into it; and nobody else complained so far either): https://trac.macports.org/ticket/50426 The initial builds failed, see for example: https://build.macports.org/builders/buildports-mtln-x86_64/builds/27442 but judging from http://packages.macports.org/geant4.10.2/ it seems as if the "build all ports" picked up and uploaded the "broken" package with "no questions asked". Shouldn't this be fixed somehow? (Not just the port, but also the behaviour.) Or did the package automagically start to work properly? I don't dare to even start parsing the logs from the all-ports build. The progress log from the same buildslave https://build.macports.org/builders/buildports-mtln-x86_64/builds/28037/steps/compile/logs/progress says "package found, not building again". Mojca ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Distinguishing between deactivated ports than I want to keep and outdated port I no longer care about
Hi, On Wed, Feb 24, 2016 at 01:56:55AM -0600, Ryan Schmidt wrote: > > Is there any equivalent of "port installed" that also shows whether > > a port was requested > > No, but you can show installed requested ports with "port installed > requested" and installed unrequested ports with "port installed > unrequested". If you want a combined list you could use: > > (port -q installed requested | sed 's/$/ (requested)/' && port -q installed > unrequested | sed 's/$/ (unrequested)/') | sort port installed \ inactive and \ unrequested and not \ ( $(port -q echo requested | sed -E 's/^/rdependentof:/') \) might give you exactly the list you're looking for? Because I'm lacking a test setup for this I cannot verify that this works as I think it should, though. > > and the size of .tar.bz2 with binaries? > > To see the disk space used by the installed files of a port, you can use: > > port space name-of-port > > I'm not sure if that includes the size of the .tbz2 archive file. To get that > separately, you can look at: > > ls -l /opt/local/var/macports/software/name-of-port/ Or rather: ls -l "$(port -q location "$portname")" -- Clemens ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: where Xcode 3.1 / command line tools ...
> On 24 Feb 2016, at 16:28, Ryan Schmidtwrote: > > On Feb 24, 2016, at 09:08, petr <9...@ingv.it> wrote: >> >> >> Hi I am trying to install Macports on an old OS X 10.6 system, but have >> difficulties to get/find Xcode 3.1 and the command line tools. Is there a >> place where they can be downloaded. > > Unless you're testing for a specific problem, you should use Xcode 3.2.6 on > Snow Leopard. Thanks Ryan for your hint, it saved me quite some network capacity ;-) For distraction I confused the requirements for Snow Leopard and Leopard. ~petr ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: where Xcode 3.1 / command line tools ...
On Feb 24, 2016, at 09:08, petr <9...@ingv.it> wrote: > > > Hi I am trying to install Macports on an old OS X 10.6 system, but have > difficulties to get/find Xcode 3.1 and the command line tools. Is there a > place where they can be downloaded. Unless you're testing for a specific problem, you should use Xcode 3.2.6 on Snow Leopard. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: where Xcode 3.1 / command line tools ...
On 24/02/16 15:13, Brandon Allbery wrote: On Wed, Feb 24, 2016 at 10:12 AM, Chris Jones> wrote: Been ages since I ran 10.6, so I might have forgotten where things are in that OS, but have you checked the OSX App Store for Xcode ? Xcode before 4.0 was not available via the App Store, as it installed under /Developer instead of as a standalone app bundle. Fair enough... According to http://guide.macports.org/#installing.xcode Xcode for OSX10.6 is available via the developer website, and indeed if I followed the link in the above I was able to find it pretty easily... Just search for 'Xcode 3' Chris ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: where Xcode 3.1 / command line tools ...
On Wed, Feb 24, 2016 at 10:12 AM, Chris Joneswrote: > Been ages since I ran 10.6, so I might have forgotten where things are in > that OS, but have you checked the OSX App Store for Xcode ? Xcode before 4.0 was not available via the App Store, as it installed under /Developer instead of as a standalone app bundle. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: where Xcode 3.1 / command line tools ...
Been ages since I ran 10.6, so I might have forgotten where things are in that OS, but have you checked the OSX App Store for Xcode ? On 24/02/16 15:08, petr wrote: Hi I am trying to install Macports on an old OS X 10.6 system, but have difficulties to get/find Xcode 3.1 and the command line tools. Is there a place where they can be downloaded. I have a ADC account and I used to find them there, but this seems not to be possible any more. Any tips? Thanks a lot! ~petr ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
where Xcode 3.1 / command line tools ...
Hi I am trying to install Macports on an old OS X 10.6 system, but have difficulties to get/find Xcode 3.1 and the command line tools. Is there a place where they can be downloaded. I have a ADC account and I used to find them there, but this seems not to be possible any more. Any tips? Thanks a lot! ~petr ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev