On 9/30/2010 11:59 PM, Dominic Fandrey wrote:
I've been thinking whether I could abandon the assumption that there
is only one package per origin in pkg_upgrade. I decided against it,
because the change would be too fundamental. If the assumption was
scrapped, there would no longer be a unique i
On 01/10/2010 01:04, Doug Barton wrote:
> On 9/29/2010 1:57 PM, Dmitry Pryanishnikov wrote:
>> Hello!
>>
>> 2010/9/28 Doug Barton:
>>>
>>> I would also argue that there is a fundamental assumption in the ports
>>> infrastructure that what you're doing here (installing both versions
>>> on the
>>> s
On 9/29/2010 1:57 PM, Dmitry Pryanishnikov wrote:
Hello!
2010/9/28 Doug Barton:
I would also argue that there is a fundamental assumption in the ports
infrastructure that what you're doing here (installing both versions on the
same system) is not supported. The ability to make the version of t
> The reason is because PORTSDIR has not been defined at this point.
> The PORTSDIR variable is defined in /usr/ports/Mk/bsd.port.mk. Also
> bsd.port.mk doesn't get included until after the master port's
> Makefile gets included.
Oh yes, you're absolutely right. I completely forgot that bsd.port
On Wed, Sep 29, 2010 at 10:40 PM, Scot Hetzel wrote:
> On Wed, Sep 29, 2010 at 2:53 AM, Klaus T. Aehlig wrote:
>>
>> Hi everybody,
>>
>> sorry for the noise.
>>
>>> > MASTERDIR= ${.CURDIR}/../py-httplib2
>>>
>>> shouldn't that be
>>>
>>> MASTERDIR=${PORTSDIR}/www/py-httplib2
>>>
>>> Or have I mis
On Wed, Sep 29, 2010 at 2:53 AM, Klaus T. Aehlig wrote:
>
> Hi everybody,
>
> sorry for the noise.
>
>> > MASTERDIR= ${.CURDIR}/../py-httplib2
>>
>> shouldn't that be
>>
>> MASTERDIR=${PORTSDIR}/www/py-httplib2
>>
>> Or have I misunderstood something here?
>
> I obviously did. At least the example
Hello!
2010/9/28 Doug Barton :
>> Those packages (py26-httplib2 vs py31-httplib2) do not
>> conflict (they may be used simultaneously, don't overwrite each
>> other's files etc.). But they have single origin, which seems to
>> confuse the portmaster:
>>
>> PYTHON_VERSION=python2.6 portmaster www/p
> MASTERDIR= ${.CURDIR}/../py-httplib2
shouldn't that be
MASTERDIR=${PORTSDIR}/www/py-httplib2
Or have I misunderstood something here?
Best regards,
Klaus
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-po
Hi everybody,
sorry for the noise.
> > MASTERDIR= ${.CURDIR}/../py-httplib2
>
> shouldn't that be
>
> MASTERDIR=${PORTSDIR}/www/py-httplib2
>
> Or have I misunderstood something here?
I obviously did. At least the example in porters' handbook and
all slave ports use ${.CURDIR}/../ Could some
On Tue, Sep 28, 2010 at 1:30 PM, Dmitry Pryanishnikov
wrote:
> Hello!
>
> I'm trying to install Python additional ports (e.g. www/py-httplib2)
> for different Python versions (2.6 and 3.1) in the same system using
> the portmaster. Those packages (py26-httplib2 vs py31-httplib2) do not
> conflict
On 9/28/2010 11:30 AM, Dmitry Pryanishnikov wrote:
Hello!
I'm trying to install Python additional ports (e.g. www/py-httplib2)
for different Python versions (2.6 and 3.1) in the same system using
the portmaster. Those packages (py26-httplib2 vs py31-httplib2) do not
conflict (they may be used
11 matches
Mail list logo
