Re: BASE_PKGPATH in PLIST [omniORB port]
2007/7/12, Jacob Meuser [EMAIL PROTECTED]:
On Thu, Jul 12, 2007 at 11:30:28AM +0200, Landry Breuil wrote:
Hello,
working on various ports, i've seen that make plist puts ${BASE_PKGPATH}
in
my PLIST / PFRAG.shared where normally there should be the package name
in
clear.
Where can this come from ? Is it normal ?
look at SUBST_VARS description in bsd.port.mk(5)
I've just updated usr.sbin/pkg_add and ports/infrastructure, doesn't
seem to
change this.
For a port installing python files in
lib/python${MODPY_VERSION}/site-packages, i suppose i need
MODULES=lang/python ? Does it imply RUN/BUILD_DEPENDS on python24 ?
MODULES have .mk files in ${PORTSDIR}/infrastructure/mk/
quick grep for MODULES in bsd.port.mk(5) comes up empty though. not
sure how to best describe them.
/usr/ports/infrastructure/mk/python.port.mk leads to
${PORTSDIR}/lang/python/python.port.mk, which shows MODPY_RUN_DEPENDS=
:python-${MODPY_VERSION}*:lang/python/${MODPY_VERSION}
So i think using lang/python module in a Makefile automagically sets python
as a RUN_DEPENDS :)
Landry
Re: BASE_PKGPATH in PLIST [omniORB port]
2007/7/12, Stuart Henderson [EMAIL PROTECTED]:
On 2007/07/12 17:32, Rui Reis wrote:
On Thu, Jul 12, 2007 at 11:30:28AM +0200, Landry Breuil wrote:
Hello,
working on various ports, i've seen that make plist puts
${BASE_PKGPATH} in
my PLIST / PFRAG.shared where normally there should be the package
name in
clear.
Where can this come from ? Is it normal ?
yes, because you are running make update-plist at the wrong dir.
If update-plist needs running from a certain dir, it needs documenting,
there's nothing in either porting.html or bsd.port.mk(5) about this, so
one would assume to just run it in /usr/ports/mystuff/foo or wherever.
And it does all seem to work ok even with ${BASE_PKGPATH} in PLIST..
No, i've seen various errors with it, like installing stuff in
include/devel/myport, or creating a lib/devel/mylib.so... weird behaviour.
But i maw be wrong, it was during the refactoring of pkg_add.
Landry
Re: BASE_PKGPATH in PLIST [omniORB port]
On Fri, Jul 13, 2007 at 09:57:35AM +0200, Landry Breuil wrote:
2007/7/12, Jacob Meuser [EMAIL PROTECTED]:
On Thu, Jul 12, 2007 at 11:30:28AM +0200, Landry Breuil wrote:
Hello,
working on various ports, i've seen that make plist puts ${BASE_PKGPATH}
in
my PLIST / PFRAG.shared where normally there should be the package name
in
clear.
Where can this come from ? Is it normal ?
look at SUBST_VARS description in bsd.port.mk(5)
I've just updated usr.sbin/pkg_add and ports/infrastructure, doesn't
seem to
change this.
For a port installing python files in
lib/python${MODPY_VERSION}/site-packages, i suppose i need
MODULES=lang/python ? Does it imply RUN/BUILD_DEPENDS on python24 ?
MODULES have .mk files in ${PORTSDIR}/infrastructure/mk/
quick grep for MODULES in bsd.port.mk(5) comes up empty though. not
sure how to best describe them.
MODULES do not need to have stuff in infrastructure/mk. In fact, we
no longer put most of them there, and I should zap the unneeded ones.
They're mostly not documented because there is still some arcane art
involved, due to when they are parsed, and what they are allowed to do,
if you do not want to run into issues later.
This is on my list of things to fix eventually. It was intentionally so.
Specifically, I wanted to get a better feel to what was appropriate before
documenting stuff...
BASE_PKGPATH in PLIST [omniORB port]
Hello,
working on various ports, i've seen that make plist puts ${BASE_PKGPATH} in
my PLIST / PFRAG.shared where normally there should be the package name in
clear.
Where can this come from ? Is it normal ?
I've just updated usr.sbin/pkg_add and ports/infrastructure, doesn't seem to
change this.
For a port installing python files in
lib/python${MODPY_VERSION}/site-packages, i suppose i need
MODULES=lang/python ? Does it imply RUN/BUILD_DEPENDS on python24 ?
Thanks for any hint,
Landry
Ps: just for clarification, here's the rough makefile of the port i'm
working on :
# $OpenBSD$
COMMENT=high performance CORBA ORB for C++ and Python
DISTNAME= omniORB-4.1.0
SHARED_LIBS=COS4 1.0 \
COSDynamic4 1.0 \
omniCodeSets4 1.0 \
omniConnectionMgmt4 1.0 \
omniDynamic4 1.0 \
omniORB4 1.0 \
omnithread 3.3
CATEGORIES= devel
HOMEPAGE= http://omniorb.sourceforge.net/
MAINTAINER= Landry Breuil [EMAIL PROTECTED]
# LGPL, GPL
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=omniorb/}
MODULES=lang/python
CONFIGURE_STYLE=gnu
USE_GMAKE= Yes
MAKE_FILE= GNUmakefile
.include bsd.port.mk
Re: BASE_PKGPATH in PLIST [omniORB port]
On Thu, Jul 12, 2007 at 11:30:28AM +0200, Landry Breuil wrote:
Hello,
working on various ports, i've seen that make plist puts ${BASE_PKGPATH} in
my PLIST / PFRAG.shared where normally there should be the package name in
clear.
Where can this come from ? Is it normal ?
yes, because you are running make update-plist at the wrong dir.
I've just updated usr.sbin/pkg_add and ports/infrastructure, doesn't seem to
change this.
For a port installing python files in
lib/python${MODPY_VERSION}/site-packages, i suppose i need
MODULES=lang/python ? Does it imply RUN/BUILD_DEPENDS on python24 ?
Thanks for any hint,
Landry
Ps: just for clarification, here's the rough makefile of the port i'm
working on :
# $OpenBSD$
COMMENT=high performance CORBA ORB for C++ and Python
DISTNAME= omniORB-4.1.0
SHARED_LIBS=COS4 1.0 \
COSDynamic4 1.0 \
omniCodeSets4 1.0 \
omniConnectionMgmt4 1.0 \
omniDynamic4 1.0 \
omniORB4 1.0 \
omnithread 3.3
CATEGORIES= devel
HOMEPAGE= http://omniorb.sourceforge.net/
MAINTAINER= Landry Breuil [EMAIL PROTECTED]
# LGPL, GPL
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=omniorb/}
MODULES=lang/python
CONFIGURE_STYLE=gnu
USE_GMAKE= Yes
MAKE_FILE= GNUmakefile
.include bsd.port.mk
Re: BASE_PKGPATH in PLIST [omniORB port]
On 2007/07/12 17:32, Rui Reis wrote:
On Thu, Jul 12, 2007 at 11:30:28AM +0200, Landry Breuil wrote:
Hello,
working on various ports, i've seen that make plist puts ${BASE_PKGPATH} in
my PLIST / PFRAG.shared where normally there should be the package name in
clear.
Where can this come from ? Is it normal ?
yes, because you are running make update-plist at the wrong dir.
If update-plist needs running from a certain dir, it needs documenting,
there's nothing in either porting.html or bsd.port.mk(5) about this, so
one would assume to just run it in /usr/ports/mystuff/foo or wherever.
And it does all seem to work ok even with ${BASE_PKGPATH} in PLIST..
Re: BASE_PKGPATH in PLIST [omniORB port]
On Thu, Jul 12, 2007 at 11:30:28AM +0200, Landry Breuil wrote:
Hello,
working on various ports, i've seen that make plist puts ${BASE_PKGPATH} in
my PLIST / PFRAG.shared where normally there should be the package name in
clear.
Where can this come from ? Is it normal ?
look at SUBST_VARS description in bsd.port.mk(5)
I've just updated usr.sbin/pkg_add and ports/infrastructure, doesn't seem to
change this.
For a port installing python files in
lib/python${MODPY_VERSION}/site-packages, i suppose i need
MODULES=lang/python ? Does it imply RUN/BUILD_DEPENDS on python24 ?
MODULES have .mk files in ${PORTSDIR}/infrastructure/mk/
quick grep for MODULES in bsd.port.mk(5) comes up empty though. not
sure how to best describe them.
--
[EMAIL PROTECTED]
SDF Public Access UNIX System - http://sdf.lonestar.org
Re: BASE_PKGPATH in PLIST [omniORB port]
On Thu, Jul 12, 2007 at 06:07:41PM +0100, Stuart Henderson wrote:
On 2007/07/12 17:32, Rui Reis wrote:
On Thu, Jul 12, 2007 at 11:30:28AM +0200, Landry Breuil wrote:
Hello,
working on various ports, i've seen that make plist puts ${BASE_PKGPATH}
in
my PLIST / PFRAG.shared where normally there should be the package name
in
clear.
Where can this come from ? Is it normal ?
yes, because you are running make update-plist at the wrong dir.
If update-plist needs running from a certain dir, it needs documenting,
there's nothing in either porting.html or bsd.port.mk(5) about this, so
one would assume to just run it in /usr/ports/mystuff/foo or wherever.
And it does all seem to work ok even with ${BASE_PKGPATH} in PLIST..
I would assume /usr/ports/mystuff/category/foo
