On 2014-2-11 03:01 , Peter Danecek wrote:
>
> I assume for port groups the concept of maintainership does not apply.
Yeah, portgroups are pretty much treated like an extension of base
(which is actually where they were formerly kept).
- Josh
___
macpor
peter.dane...@bo.ingv.it writes:
> Hi MacPorts Developers,
> Hi Sean,
>
> I am about to upgrade one of my ports which is using the "Fortran Recipe".
> Now, there is the "Compilers Portgroup" available and from what I understand
> I would serve to eliminate some code from that Portfile.
Yep, t
3.1.1 will contain the fix, which is related to xattrs
On Sun, Feb 9, 2014 at 7:02 PM, MacPorts wrote:
> #40803: Rsync 3.1.0 released
> --+--
> Reporter: jones@... | Owner: jimjag@...
> Type: update | Status: new
> Priority: Nor
Hi all,
I happened to look up some details in the Python portgroup and step across the
use of `!=` and `==` where probably "eq" and "ne" would be more appropriate.
http://trac.macports.org/browser/trunk/dports/_resources/port1.0/group/python-1.0.tcl#L89
I assume for port groups the concept of
Hi MacPorts Developers,
Hi Sean,
I am about to upgrade one of my ports which is using the "Fortran Recipe". Now,
there is the "Compilers Portgroup" available and from what I understand I would
serve to eliminate some code from that Portfile.
Unfortunately, I have no complete picture of how th
Hi,
> I would like to try MacPorts’ current trunk version.
>
> How do I do this seamlessly, i.e. is it necessary to reinstall MacPorts from
> scratch, or can I somehow manage to keep all installed ports in place while
> just switching from my existing installation to trunk??
You can just install
