yes, so @pkgpath was added after 3.8. using current ports on release
versions is not supported. see FAQ 15.4.1.
If so, what is the procedure to get around it?
It's fairly easy: install a snapshot..
Hi,
has anybody managed to build Python 2.4.2 from
ports created in 24/12/2005? Mine tries to
install Berkeley db which fails for
@pkgpath in db's file PKLIST:
Unknown element: pkgpath etc...
I am using official v3.8.
Building Berkeley from sources succeeds
but building Python does not.
On Sun, Dec 25, 2005 at 06:59:01PM +0200, Pekka Niiranen wrote:
Hi,
has anybody managed to build Python 2.4.2 from
ports created in 24/12/2005? Mine tries to
install Berkeley db which fails for
@pkgpath in db's file PKLIST:
Unknown element: pkgpath etc...
I am using official v3.8.
On Sun, Dec 25, 2005 at 06:59:01PM +0200, Pekka Niiranen wrote:
Hi,
has anybody managed to build Python 2.4.2 from
ports created in 24/12/2005? Mine tries to
install Berkeley db which fails for
@pkgpath in db's file PKLIST:
Unknown element: pkgpath etc...
I am using official v3.8.
* Pekka Niiranen [2005-12-25]:
[-current ports tree on -stable base]
If so, what is the procedure to get around it?
There is no such procedure.
How can I compile Python then? I tried to just
Why don't you just use the 3.8 ports tree?
remove @pkgpath line from PKLIST, but compilation
Nikolay Sturm wrote:
* Pekka Niiranen [2005-12-25]:
[-current ports tree on -stable base]
If so, what is the procedure to get around it?
There is no such procedure.
How can I compile Python then? I tried to just
Why don't you just use the 3.8 ports tree?
Because the Python version
learning to port something is quite different from mixing current and
stable.
The former is fine for this list, the latter is not fine for any OpenBSD
list.
Some of us charge money if you really want to do things not supportable
by OpenBSD (aka not enough desire/developer resources to even
