On Sep 30, 2013, at 12:47 PM, Ryan Schmidt wrote:
> On Sep 30, 2013, at 11:18, Bradley Giesbrecht wrote:
>
>> Is there an example Portfile with multiple distfiles of differing
>> extract.suffix?
>
> I can't think of an example at the moment, but you could grep Portfiles for
> those with a po
On Sep 30, 2013, at 14:19, Bradley Giesbrecht wrote:
> I wonder how difficult it would be to add an extract block to a Portfile and
> use "command_exec extract" for each distfile changing things like use_zip
> along the way?
Probably a lot more complicated than just writing one `system` line.
On Sep 30, 2013, at 9:47 AM, Ryan Schmidt wrote:
>
> On Sep 30, 2013, at 11:18, Bradley Giesbrecht wrote:
>
>> Is there an example Portfile with multiple distfiles of differing
>> extract.suffix?
>
> I can't think of an example at the moment, but you could grep Portfiles for
> those with a
On 2013-09-30 16:36, Peter Danecek wrote:
>
> Sorry for this post, which maybe somewhat off-topic, but I am a bit confused
> now. I had never to go into these details on MacOS so far.
>
> --- snip ---
>
> petr% cat /etc/group | grep admin
> admin:*:80:root
> _lpadmin:*:98:
>
> petr% id
> uid=5
On Sep 30, 2013, at 11:18, Bradley Giesbrecht wrote:
> Is there an example Portfile with multiple distfiles of differing
> extract.suffix?
I can't think of an example at the moment, but you could grep Portfiles for
those with a post-extract block. MacPorts only handles a single type of
distf
On 2013-10-1 01:20 , Peter Danecek wrote:
>
> Well, if I am now understanding right, for perl, ar, randlib are not set to
> default values by macports. Is it save to point these to the systems provided
> versions with the absolute path?
>
> something like:
> PERL=/usr/bin/perl
> AR=/usr/bin
Is there an example Portfile with multiple distfiles of differing
extract.suffix?
Regards,
Bradley Giesbrecht (pixilla)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On Sep 30, 2013, at 10:20, Peter Danecek wrote:
> Well, if I am now understanding right, for perl, ar, randlib are not set to
> default values by macports.
That's right.
> Is it save to point these to the systems provided versions with the absolute
> path?
>
> something like:
> PERL=/usr/b
Hi,
I just wanted to say that I upgraded Geant4. The new subports are now
called geant4.9.5 and geant4.9.6 and may be installed side-by-side.
(If anyone wants to test version 10.0 you only need to uncomment/move
a single line.)
The build is now CMake-based and the easiest way to compile you code
On Sep 30, 2013, at 17:08 , Joshua Root wrote:
> On 2013-10-1 00:17 , Peter Danecek wrote:
>>
>> Hi all,
>>
>> I am currently trying to setup a port. The "configure script" (not a
>> standard GNU approach) does set makefile variables for CC, AR, PERL, etc.,
>> but does not respect the sett
On 2013-10-1 00:17 , Peter Danecek wrote:
>
> Hi all,
>
> I am currently trying to setup a port. The "configure script" (not a standard
> GNU approach) does set makefile variables for CC, AR, PERL, etc., but does
> not respect the setting for environment variables.
>
> During configure phase m
Sorry for this post, which maybe somewhat off-topic, but I am a bit confused
now. I had never to go into these details on MacOS so far.
--- snip ---
petr% cat /etc/group | grep admin
admin:*:80:root
_lpadmin:*:98:
petr% id
uid=502(petr) gid=20(staff)
groups=20(staff),401(com.apple.access_scre
On Sep 29, 2013, at 17:03, Josh Watzman wrote:
> Would someone mind to review and commit my proposed update for the port
> "awesome"? https://trac.macports.org/ticket/39497 The trac ticket has
> been open for months, the version currently in macports trunk actually
> fails to build (and has for a
On Mon, Sep 30, 2013 at 04:17:03PM +0200, Peter Danecek wrote:
> During configure phase macports sets such environment variables,
> right? In particular I am aware of the ones for the compilers to use.
> However, searching the documentation I have not found a comprehensive.
> Does such a list appea
Hi all,
I am currently trying to setup a port. The "configure script" (not a standard
GNU approach) does set makefile variables for CC, AR, PERL, etc., but does not
respect the setting for environment variables.
During configure phase macports sets such environment variables, right? In
partic
Could someone with commit access take a look at
https://trac.macports.org/ticket/40117 for me please? My `rev-upgrade`
keeps choking on collada-dom...
Thanks,
Eric
-- Forwarded message --
From: MacPorts
Date: Sat, Sep 7, 2013 at 9:46 PM
Subject: Re: [MacPorts] #40117: collada-dom
On Sep 30, 2013, at 02:42, mo...@macports.org wrote:
> Revision: 111725
> https://trac.macports.org/changeset/111725
> Author: mo...@macports.org
> Date: 2013-09-30 00:42:36 -0700 (Mon, 30 Sep 2013)
> Log Message:
> ---
> geant4: add a post-activate note about port select/s
On Sep 29, 2013, at 16:35, "M. Daniel Becque" wrote:
> I noticed that unpaper is now abandoned. Looking at other port files I
> thought I would make a naive stab at a port update for unpaper. I contacted
> flameeyes and he reponded with this:
> "In general I think you should look at the mos
18 matches
Mail list logo
