On Tue, Oct 02, 2012 at 00:18:07 +0400, Dmitry Sivachenko wrote:
> On 10/1/12 10:44 PM, Chris Rees wrote:
> > However, it is still possible to have the "first installed wins" logic
> > using a pkg-install script instead of in the Makefile, this would
> > solve the package problems. Are you intere
On 1 October 2012 14:20, Ruslan Mahmatkhanov wrote:
> So we returned to initial question :). Is this acceptable to do this,
> because it will require all the distinfos change "w/o a reason"? I didn't
> see anything criminal there, but other people may know better.
distinfo can change. The concern
On 10/1/12 10:44 PM, Chris Rees wrote:
However, it is still possible to have the "first installed wins" logic
using a pkg-install script instead of in the Makefile, this would
solve the package problems. Are you interested if I were to implement
that? Chris
I think that "first wins" logic i
On 1 October 2012 19:20, Ruslan Mahmatkhanov wrote:
> Li-Wen Hsu wrote on 01.10.2012 22:11:
>
>> On Mon, Oct 01, 2012 at 22:03:48 +0400, Ruslan Mahmatkhanov wrote:
>>>
>>> Li-Wen Hsu wrote on 01.10.2012 21:51:
EXTRACT_SUFX?= .tgz
PYTHON_DISTFILE= Python-${PYTHON_PORTVERSION:S/.
On 1 October 2012 18:39, Li-Wen Hsu wrote:
> On Thu, Sep 27, 2012 at 15:22:03 +0400, Dmitry Sivachenko wrote:
>> On 26.09.2012 17:00, Li-Wen Hsu wrote:
>> >
>> > I think this patch is good. And I am thinking about also modifying
>> > other lang/python{2,3}X ports, thus we may need to beware of
>>
Li-Wen Hsu wrote on 01.10.2012 22:11:
On Mon, Oct 01, 2012 at 22:03:48 +0400, Ruslan Mahmatkhanov wrote:
Li-Wen Hsu wrote on 01.10.2012 21:51:
EXTRACT_SUFX?= .tgz
PYTHON_DISTFILE= Python-${PYTHON_PORTVERSION:S/.rc/rc/}}${EXTRACT_SUFX}
Yes, I also bow to this option.
then we can define USE_
On, Mon Oct 01, 2012, Li-Wen Hsu wrote:
> On Mon, Oct 1, 2012 at 10:10 PM, Marcus von Appen wrote:
> >
> > Ruslan Mahmatkhanov :
> >
> >> Hello,
> >>
> >> The python.org ftp provides lang/pythonXX source tarballs in a many
> >> formats:
> >> - tar.bz2
> >> - tar.xz
> >> - tgz
> >>
> >> Using .tgz
On Mon, Oct 01, 2012 at 22:03:48 +0400, Ruslan Mahmatkhanov wrote:
> Li-Wen Hsu wrote on 01.10.2012 21:51:
> >
> > EXTRACT_SUFX?= .tgz
> > PYTHON_DISTFILE= Python-${PYTHON_PORTVERSION:S/.rc/rc/}}${EXTRACT_SUFX}
>
> Yes, I also bow to this option.
>
> > then we can define USE_XZ= yes in the ports
Li-Wen Hsu wrote on 01.10.2012 21:51:
On Mon, Oct 1, 2012 at 10:10 PM, Marcus von Appen wrote:
Ruslan Mahmatkhanov :
Hello,
The python.org ftp provides lang/pythonXX source tarballs in a many
formats:
- tar.bz2
- tar.xz
- tgz
Using .tgz is not in sports-way this days, so I'd prefer to use
On Mon, Oct 1, 2012 at 10:10 PM, Marcus von Appen wrote:
>
> Ruslan Mahmatkhanov :
>
>> Hello,
>>
>> The python.org ftp provides lang/pythonXX source tarballs in a many
>> formats:
>> - tar.bz2
>> - tar.xz
>> - tgz
>>
>> Using .tgz is not in sports-way this days, so I'd prefer to use tar.xz for
>>
On Thu, Sep 27, 2012 at 15:22:03 +0400, Dmitry Sivachenko wrote:
> On 26.09.2012 17:00, Li-Wen Hsu wrote:
> >
> > I think this patch is good. And I am thinking about also modifying
> > other lang/python{2,3}X ports, thus we may need to beware of
> > confliction on bin/python{2,3} between lang/pyth
On Wed, Sep 26, 2012 at 17:17:20 +0400, Дмитрий Сиваченко wrote:
> On 9/26/12 5:00 PM, Li-Wen Hsu wrote:
> >
> > I think this patch is good. And I am thinking about also modifying
> > other lang/python{2,3}X ports, thus we may need to beware of
> > confliction on bin/python{2,3} between lang/pytho
Ruslan Mahmatkhanov :
Hello,
The python.org ftp provides lang/pythonXX source tarballs in a many formats:
- tar.bz2
- tar.xz
- tgz
Using .tgz is not in sports-way this days, so I'd prefer to use
tar.xz for new versions. But I can't actually choose there because
tarball format is hardcoded
Hello,
The python.org ftp provides lang/pythonXX source tarballs in a many formats:
- tar.bz2
- tar.xz
- tgz
Using .tgz is not in sports-way this days, so I'd prefer to use tar.xz
for new versions. But I can't actually choose there because tarball
format is hardcoded in Mk/bsd.python.mk as PY
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
15 matches
Mail list logo