On Jan 10, 2013, at 21:59, Ryan Stonecipher wrote:
> Ryan Schmidt wrote:
>
>> There are other nuances of unified ports. The best documentation is to read
>> existing ports using the portgroup—there are tons of them.
>
> Many ports written in the differing styles of several maintainers are not
> Date: Thu, 10 Jan 2013 12:21:56 -0600
> From: Ryan Schmidt
> Subject: Re: Unified Python portgroup
>
> There are other nuances of unified ports. The best documentation is to
> read existing ports using the portgroup?there are tons of them.
Many ports written in the differing
On Jan 10, 2013, at 16:51, Freek Dijkstra wrote:
> On 10-01-2013 15:25, Jeremy Lavergne wrote:
>
>> You need:
>> sudo port -d install subport=py27-pdfrw
>
> Thanks Jeremy,
>
> Your answer is spot-on. With this syntax, the modified Portgroup behaved
> as it should.
>
> I never made the mental
On 11-01-2013 00:06, Jeremy Lavergne wrote:
> When building portindex, the unnamed versions aren't created so users won't
> ever stumble upon them.
Ah, thanks again. I now (slowly) start to understand how subports work.
Freek
___
macports-dev mailing
>>> [...] "python.versions 25 26 27". To my surprise the
>>> following command was accepted:
>>>
[root@lampje] Code/macports/py-pdfrw# port install subport=py32-pdfrw
---> Computing dependencies for py32-pdfrw
> [...]
---> Configuring py32-pdfrw
---> Building py32-pdfrw
On 10-01-2013 23:57, Jeremy Lavergne wrote:
>> [...] "python.versions 25 26 27". To my surprise the
>> following command was accepted:
>>
>>> [root@lampje] Code/macports/py-pdfrw# port install subport=py32-pdfrw
>>> ---> Computing dependencies for py32-pdfrw
[...]
>>> ---> Configuring py32-pdfrw
On 10-01-2013 15:25, Jeremy Lavergne wrote:
> You need:
> sudo port -d install subport=py27-pdfrw
Thanks Jeremy,
Your answer is spot-on. With this syntax, the modified Portgroup behaved
as it should.
I never made the mental link between "Unified portgroup" and "subport"
otherwise I would have p
On Jan 10, 2013, at 08:25, Jeremy Lavergne wrote:
>> That is actually not a bug! You're trying to install it directly from the
>> directory, which is equivalent to running `port -d install py-pdfrw`. Now,
>> since you didn't provide a py24-* subport, the behaviour defined in the
>> python port
> That is actually not a bug! You're trying to install it directly from the
> directory, which is equivalent to running `port -d install py-pdfrw`. Now,
> since you didn't provide a py24-* subport, the behaviour defined in the
> python portgroup for running install without specifying a version (
On 10/gen/2013, at 09:57, Freek Dijkstra wrote:
> Hi all,
>
> Is there any documentation for the unified Python portgroup? The guide
> does not yet mention it, and searching the mailing list only resulted in
> one thread.
I don't think there's a guide other than peer
Hi all,
Is there any documentation for the unified Python portgroup? The guide
does not yet mention it, and searching the mailing list only resulted in
one thread.
I submitted a Portfile for py27-pdfrw, and was asked to modify it to use
the unified python 1.0 portgroup. I'm happy to do so
for python2 and version 2.x for python3. Is there
> a way to achieve this using the unified python portgroup?
There's nothing in the portgroup to handle this case. You can change
anything you want in a subport though. Whether this is a good idea in
any particular case depends on how it aff
this using the unified python portgroup?
Cheers
Adam
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
13 matches
Mail list logo
