Re: [SOLVED] Re: optionsng ignores /var/db/ports//options
On Mon, Jun 04, 2012 at 09:36:35PM -0400, Greg Larkin wrote: > >> Hi Roland, > >> > >> I don't think you want to hardcode the "py27-" in the variable > >> assignment, since it ties the filename to a specific version of > >> Python. Check PYTHON_PKGNAMEPREFIX, and it should adjust itself > >> as the Python version changes. > > > > Actually, if I understood correctly, the fact that > > PYTHON_PKGNAMEPREFIX _changes_ from py- to py27- in different parts > > of the included .mk files is what causes the problem in the first > > place. So I did this on purpose. > > > > Roland > > Hi Roland, > > Ok, I should have read the previous thread emails more closely. At > any rate, putting a specific Python version into the name of the > OPTIONSFILE seems a bit confusing. OTOH, it keeps the name of /var/db/port//options in line with the packagename (without the version number), and it is what most Python-based ports seem to do. > Could you achieve the same outcome > by putting "py-" instead of "py27-" in the name? Yes, more or less. There are ports that do that as well. But the majority seem to include the python version. AFAICT to be able to install the same package with different options for different Python versions. Anyway, the PR for updating my port is out. And one of the maintainers is working on some of the warts of the ports system. It turns out that this bug was already reported two years ago. But the ports system is quite a complex beast... Roland -- R.F.Smith http://rsmith.home.xs4all.nl/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpTktPUUskY4.pgp Description: PGP signature
Re: [SOLVED] Re: optionsng ignores /var/db/ports//options
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/4/12 5:25 PM, Roland Smith wrote:
> On Mon, Jun 04, 2012 at 04:01:27PM -0400, Greg Larkin wrote:
>>> Well, it was a bug, but not particularly in showconfig alone,
>>> see below.
>>>
> If not, then something odd is happening, as your port
> looks perfectly OK to me. Are you using a ports tree
> updated within about the last 48 hours or so? I know there
> were some bug fixes went in to all FOO_DESC lines to
> contain (brackets) and other syntactically significant
> characters.
I updated my ports tree this afternoon. The really weird
thing is that I tested 'make config' in several other ports
where it worked fine...
> PS. Asking this on freebsd-ports@... might be a good idea.
>>>
>>> The bad news is that it was a bug in the ports system. It
>>> turned out that because of the way the unique name of the port
>>> was set (which happens twice), the options file is not read
>>> from the same directory that it is written to! Thanks to
>>> Baptiste Daroussin for clueing me in in this. I've gained a new
>>> respect for the people maintaining the ports infrastructure.
>>> :-) It's kind of amazing it works as well as it does.
>>>
>>> The good news is that there are several workarounds. For
>>> future reference, the workaround that I ended up using was to
>>> set the following variable in the port makefile:
>>>
>>> OPTIONSFILE=${PORT_DBDIR}/py27-${PORTNAME}/options
>>>
>>>
>>> Roland
>>
>> Hi Roland,
>>
>> I don't think you want to hardcode the "py27-" in the variable
>> assignment, since it ties the filename to a specific version of
>> Python. Check PYTHON_PKGNAMEPREFIX, and it should adjust itself
>> as the Python version changes.
>
> Actually, if I understood correctly, the fact that
> PYTHON_PKGNAMEPREFIX _changes_ from py- to py27- in different parts
> of the included .mk files is what causes the problem in the first
> place. So I did this on purpose.
>
> Roland
Hi Roland,
Ok, I should have read the previous thread emails more closely. At
any rate, putting a specific Python version into the name of the
OPTIONSFILE seems a bit confusing. Could you achieve the same outcome
by putting "py-" instead of "py27-" in the name?
Regards,
Greg
- --
Greg Larkin
http://www.FreeBSD.org/ - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/cpucycle/ - Follow you, follow me
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/NYqIACgkQ0sRouByUApBeJACgyuHOEkwVWIdVq31XkLtd89AQ
GWsAoLzZpiKWOAe2u8sEWEM/kGvvnmT+
=JKWu
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: [SOLVED] Re: optionsng ignores /var/db/ports//options
On Mon, Jun 04, 2012 at 04:01:27PM -0400, Greg Larkin wrote:
> > Well, it was a bug, but not particularly in showconfig alone, see
> > below.
> >
> >>> If not, then something odd is happening, as your port looks
> >>> perfectly OK to me. Are you using a ports tree updated within
> >>> about the last 48 hours or so? I know there were some bug
> >>> fixes went in to all FOO_DESC lines to contain (brackets) and
> >>> other syntactically significant characters.
> >>
> >> I updated my ports tree this afternoon. The really weird thing is
> >> that I tested 'make config' in several other ports where it
> >> worked fine...
> >>
> >>> PS. Asking this on freebsd-ports@... might be a good idea.
> >
> > The bad news is that it was a bug in the ports system. It turned
> > out that because of the way the unique name of the port was set
> > (which happens twice), the options file is not read from the same
> > directory that it is written to! Thanks to Baptiste Daroussin for
> > clueing me in in this. I've gained a new respect for the people
> > maintaining the ports infrastructure. :-) It's kind of amazing it
> > works as well as it does.
> >
> > The good news is that there are several workarounds. For future
> > reference, the workaround that I ended up using was to set the
> > following variable in the port makefile:
> >
> > OPTIONSFILE=${PORT_DBDIR}/py27-${PORTNAME}/options
> >
> >
> > Roland
>
> Hi Roland,
>
> I don't think you want to hardcode the "py27-" in the variable
> assignment, since it ties the filename to a specific version of
> Python. Check PYTHON_PKGNAMEPREFIX, and it should adjust itself as
> the Python version changes.
Actually, if I understood correctly, the fact that PYTHON_PKGNAMEPREFIX
_changes_ from py- to py27- in different parts of the included .mk files is
what causes the problem in the first place. So I did this on purpose.
Roland
--
R.F.Smith http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpT3JboMQ8pu.pgp
Description: PGP signature
Re: [SOLVED] Re: optionsng ignores /var/db/ports//options
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/4/12 2:32 PM, Roland Smith wrote:
> On Sun, Jun 03, 2012 at 09:10:03PM +0200, Roland Smith wrote:
>> On Sun, Jun 03, 2012 at 07:18:26PM +0100, Matthew Seaman wrote:
>>> On 03/06/2012 17:05, Roland Smith wrote:
>>>> I've used 'make config' to set the PYCAIO option to on;
>>>>
>>>> slackbox# cat /var/db/ports/py27-py-stl/options # This file
>>>> is auto-generated by 'make config'. # Options for
>>>> py27-py-stl-3.1 _OPTIONS_READ=py27-py-stl-3.1
>>>> _FILE_COMPLETE_OPTIONS_LIST=PYCAIRO
>>>> OPTIONS_FILE_SET+=PYCAIRO
>>>>
>>>> But the port seems to ignore it:
>>>>
>>>> slackbox# make showconfig ===> The following configuration
>>>> options are available for py27-py-stl-3.1: PYCAIRO=off: Use
>>>> (py)Cairo to enable stl2pdf ===> Use 'make config' to modify
>>>> these settings
>>>>
>>>> Every time I do 'make config', the PYCAIRO option will be
>>>> unset, even if it shows as set in
>>>> /var/db/ports//options!
>>>
>>> What does
>>>
>>> % make -V PORT_OPTIONS
>>
>> slackbox# pwd /usr/ports/graphics/py-stl slackbox# make -V
>> PORT_OPTIONS DOCS EXAMPLES NLS
>>
>>> show? If PYCAIRO is set in PORT_OPTIONS, then the port is
>>> accepting your setting of the option, and you've found a bug
>>> with the showconfig target. (If so, please open a PR.)
>
> Well, it was a bug, but not particularly in showconfig alone, see
> below.
>
>>> If not, then something odd is happening, as your port looks
>>> perfectly OK to me. Are you using a ports tree updated within
>>> about the last 48 hours or so? I know there were some bug
>>> fixes went in to all FOO_DESC lines to contain (brackets) and
>>> other syntactically significant characters.
>>
>> I updated my ports tree this afternoon. The really weird thing is
>> that I tested 'make config' in several other ports where it
>> worked fine...
>>
>>> PS. Asking this on freebsd-ports@... might be a good idea.
>
> The bad news is that it was a bug in the ports system. It turned
> out that because of the way the unique name of the port was set
> (which happens twice), the options file is not read from the same
> directory that it is written to! Thanks to Baptiste Daroussin for
> clueing me in in this. I've gained a new respect for the people
> maintaining the ports infrastructure. :-) It's kind of amazing it
> works as well as it does.
>
> The good news is that there are several workarounds. For future
> reference, the workaround that I ended up using was to set the
> following variable in the port makefile:
>
> OPTIONSFILE=${PORT_DBDIR}/py27-${PORTNAME}/options
>
>
> Roland
Hi Roland,
I don't think you want to hardcode the "py27-" in the variable
assignment, since it ties the filename to a specific version of
Python. Check PYTHON_PKGNAMEPREFIX, and it should adjust itself as
the Python version changes.
Hope that helps,
Greg
- --
Greg Larkin
http://www.FreeBSD.org/ - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/cpucycle/ - Follow you, follow me
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/NFBcACgkQ0sRouByUApDtRgCgl0NvUTwexNS1TdZqqXElKWPX
SggAn1b/QRnU8rhwbtu0mebByp+IRB3A
=+ly7
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
[SOLVED] Re: optionsng ignores /var/db/ports//options
On Sun, Jun 03, 2012 at 09:10:03PM +0200, Roland Smith wrote:
> On Sun, Jun 03, 2012 at 07:18:26PM +0100, Matthew Seaman wrote:
> > On 03/06/2012 17:05, Roland Smith wrote:
> > > I've used 'make config' to set the PYCAIO option to on;
> > >
> > > slackbox# cat /var/db/ports/py27-py-stl/options
> > > # This file is auto-generated by 'make config'.
> > > # Options for py27-py-stl-3.1
> > > _OPTIONS_READ=py27-py-stl-3.1
> > > _FILE_COMPLETE_OPTIONS_LIST=PYCAIRO
> > > OPTIONS_FILE_SET+=PYCAIRO
> > >
> > > But the port seems to ignore it:
> > >
> > > slackbox# make showconfig
> > > ===> The following configuration options are available for
> > > py27-py-stl-3.1:
> > > PYCAIRO=off: Use (py)Cairo to enable stl2pdf
> > > ===> Use 'make config' to modify these settings
> > >
> > > Every time I do 'make config', the PYCAIRO option will be unset, even if
> > > it
> > > shows as set in /var/db/ports//options!
> >
> > What does
> >
> > % make -V PORT_OPTIONS
>
> slackbox# pwd
> /usr/ports/graphics/py-stl
> slackbox# make -V PORT_OPTIONS
> DOCS EXAMPLES NLS
>
> > show? If PYCAIRO is set in PORT_OPTIONS, then the port is accepting
> > your setting of the option, and you've found a bug with the showconfig
> > target. (If so, please open a PR.)
Well, it was a bug, but not particularly in showconfig alone, see below.
> > If not, then something odd is happening, as your port looks perfectly OK
> > to me. Are you using a ports tree updated within about the last 48 hours
> > or so? I know there were some bug fixes went in to all FOO_DESC lines to
> > contain (brackets) and other syntactically significant characters.
>
> I updated my ports tree this afternoon. The really weird thing is that I
> tested 'make config' in several other ports where it worked fine...
>
> > PS. Asking this on freebsd-ports@... might be a good idea.
The bad news is that it was a bug in the ports system. It turned out that
because of the way the unique name of the port was set (which happens twice),
the options file is not read from the same directory that it is written to!
Thanks to Baptiste Daroussin for clueing me in in this. I've gained a new
respect for the people maintaining the ports infrastructure. :-) It's kind of
amazing it works as well as it does.
The good news is that there are several workarounds. For future reference, the
workaround that I ended up using was to set the following variable in the port
makefile:
OPTIONSFILE=${PORT_DBDIR}/py27-${PORTNAME}/options
Roland
--
R.F.Smith http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgptSRxbItyLD.pgp
Description: PGP signature
Re: optionsng ignores /var/db/ports//options
On Sun, Jun 03, 2012 at 07:18:26PM +0100, Matthew Seaman wrote: > On 03/06/2012 17:05, Roland Smith wrote: > > I've used 'make config' to set the PYCAIO option to on; > > > > slackbox# cat /var/db/ports/py27-py-stl/options > > # This file is auto-generated by 'make config'. > > # Options for py27-py-stl-3.1 > > _OPTIONS_READ=py27-py-stl-3.1 > > _FILE_COMPLETE_OPTIONS_LIST=PYCAIRO > > OPTIONS_FILE_SET+=PYCAIRO > > > > But the port seems to ignore it: > > > > slackbox# make showconfig > > ===> The following configuration options are available for py27-py-stl-3.1: > > PYCAIRO=off: Use (py)Cairo to enable stl2pdf > > ===> Use 'make config' to modify these settings > > > > Every time I do 'make config', the PYCAIRO option will be unset, even if it > > shows as set in /var/db/ports//options! > > What does > > % make -V PORT_OPTIONS slackbox# pwd /usr/ports/graphics/py-stl slackbox# make -V PORT_OPTIONS DOCS EXAMPLES NLS > show? If PYCAIRO is set in PORT_OPTIONS, then the port is accepting > your setting of the option, and you've found a bug with the showconfig > target. (If so, please open a PR.) > > If not, then something odd is happening, as your port looks perfectly OK > to me. Are you using a ports tree updated within about the last 48 > hours or so? I know there were some bug fixes went in to all FOO_DESC > lines to contain (brackets) and other syntactically significant characters. I updated my ports tree this afternoon. The really weird thing is that I tested 'make config' in several other ports where it worked fine... > PS. Asking this on freebsd-ports@... might be a good idea. I guess I will do that. Roland -- R.F.Smith http://rsmith.home.xs4all.nl/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp5KhoOgyYfF.pgp Description: PGP signature
Re: optionsng ignores /var/db/ports//options
On 03/06/2012 17:05, Roland Smith wrote: > I've used 'make config' to set the PYCAIO option to on; > > slackbox# cat /var/db/ports/py27-py-stl/options > # This file is auto-generated by 'make config'. > # Options for py27-py-stl-3.1 > _OPTIONS_READ=py27-py-stl-3.1 > _FILE_COMPLETE_OPTIONS_LIST=PYCAIRO > OPTIONS_FILE_SET+=PYCAIRO > > But the port seems to ignore it: > > slackbox# make showconfig > ===> The following configuration options are available for py27-py-stl-3.1: > PYCAIRO=off: Use (py)Cairo to enable stl2pdf > ===> Use 'make config' to modify these settings > > Every time I do 'make config', the PYCAIRO option will be unset, even if it > shows as set in /var/db/ports//options! What does % make -V PORT_OPTIONS show? If PYCAIRO is set in PORT_OPTIONS, then the port is accepting your setting of the option, and you've found a bug with the showconfig target. (If so, please open a PR.) If not, then something odd is happening, as your port looks perfectly OK to me. Are you using a ports tree updated within about the last 48 hours or so? I know there were some bug fixes went in to all FOO_DESC lines to contain (brackets) and other syntactically significant characters. Cheers, Matthew PS. Asking this on freebsd-ports@... might be a good idea. -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
optionsng ignores /var/db/ports//options
Hi,
With the release of the new options framework for ports, I've run into a
problem trying to convert one of my ports.
The nature of the problem is that the port seems to ignore the setting stored
in /var/db/ports//options:
I've used 'make config' to set the PYCAIO option to on;
slackbox# cat /var/db/ports/py27-py-stl/options
# This file is auto-generated by 'make config'.
# Options for py27-py-stl-3.1
_OPTIONS_READ=py27-py-stl-3.1
_FILE_COMPLETE_OPTIONS_LIST=PYCAIRO
OPTIONS_FILE_SET+=PYCAIRO
But the port seems to ignore it:
slackbox# make showconfig
===> The following configuration options are available for py27-py-stl-3.1:
PYCAIRO=off: Use (py)Cairo to enable stl2pdf
===> Use 'make config' to modify these settings
Every time I do 'make config', the PYCAIRO option will be unset, even if it
shows as set in /var/db/ports//options!
My port Makefile is as follows:
port Makefile
# New ports collection makefile for:py-stl
# Date created: 28 Dec 2011
# Whom: rsm...@xs4all.nl
#
# $FreeBSD$
PORTNAME= py-stl
PORTVERSION=3.1
CATEGORIES= graphics python
MASTER_SITES= http://rsmith.home.xs4all.nl/software/
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
MAINTAINER= rsm...@xs4all.nl
COMMENT=Converts STL models to POV-Ray meshes or PostScript/PDF
images
USE_ZIP=YES
USE_PYTHON= 2.5+
USE_PYDISTUTILS=YES
CONFLICTS= stl2pov-[0-9]*
MAN1= stl2ps.1 stlinfo.1
OPTIONS_DEFINE= PYCAIRO
PYCAIRO_DESC= Use (py)Cairo to enable stl2pdf
.include
.if ${PORT_OPTIONS:MPYCAIRO}
RUN_DEPENDS+=
${PYTHON_PKGNAMEPREFIX}cairo>1.8:${PORTSDIR}/graphics/py-cairo
MAN1+= stl2pdf.1
PLIST_SUB+= STL2PDF=""
.else
PLIST_SUB+= STL2PDF="@comment "
.endif
NO_BUILD= YES
post-install:
.if ${PORT_OPTIONS:MPYCAIRO}
@${INSTALL_MAN} ${WRKSRC}/stl2pdf.1 ${MANPREFIX}/man/man1
@${MV} ${PREFIX}/bin/stl2pdf.py ${PREFIX}/bin/stl2pdf
.else
@${RM} -f ${PREFIX}/bin/stl2pdf.py
@${RM} -f ${MANPREFIX}/man/man1/stl2pdf.1*
.endif
@${INSTALL_MAN} ${WRKSRC}/stl2ps.1 ${MANPREFIX}/man/man1
@${INSTALL_MAN} ${WRKSRC}/stlinfo.1 ${MANPREFIX}/man/man1
@${MV} ${PREFIX}/bin/stl2ps.py ${PREFIX}/bin/stl2ps
@${MV} ${PREFIX}/bin/stl2pov.py ${PREFIX}/bin/stl2pov
@${MV} ${PREFIX}/bin/stlinfo.py ${PREFIX}/bin/stlinfo
@${MV}
${PYTHON_SITELIBDIR}/py_stl-${PORTVERSION}-py${PYTHON_VER}.egg-info
${PYTHON_SITELIBDIR}/${PYDISTUTILS_EGGINFO}
.include
port Makefile
I've looked at other ports makefiles and see no obvious defects. Help?
Roland
--
R.F.Smith http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpevURyMlf0Z.pgp
Description: PGP signature
Re: Ports options not coming up
On Thu, 2009-04-02 at 14:15 +0200, rasz wrote: > Da Rock wrote: > > I'd to debug this, but I'm not even sure where to start. On just one > > system since some recent updates I have no options screens coming up for > > ports. I get a blue screen and then nothing; stdout says options > > unchanged. > > > > It is a vm if that means anything? > > > > Cheers > > > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > > > > > if i understand you correctly, and this is the same thing, i have had > this happen when > building ports in a terminal emulator of sorts, particularly the xfce4 > one (and maybe kde4 konsole) > when the actual window is too small (e.g. in number of lines). i would > see the blue screen for a bit and then > options unchanged. it doesn't happen if at all if i keep the window a > good size, but i don't know about VM. You know, I followed the vm track but I never even considered the terminal! Duh! :) Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Ports options not coming up
Da Rock wrote: I'd to debug this, but I'm not even sure where to start. On just one system since some recent updates I have no options screens coming up for ports. I get a blue screen and then nothing; stdout says options unchanged. It is a vm if that means anything? Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" if i understand you correctly, and this is the same thing, i have had this happen when building ports in a terminal emulator of sorts, particularly the xfce4 one (and maybe kde4 konsole) when the actual window is too small (e.g. in number of lines). i would see the blue screen for a bit and then options unchanged. it doesn't happen if at all if i keep the window a good size, but i don't know about VM. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Ports options not coming up
I'd to debug this, but I'm not even sure where to start. On just one system since some recent updates I have no options screens coming up for ports. I get a blue screen and then nothing; stdout says options unchanged. It is a vm if that means anything? Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Ports Options
On Friday 20 February 2009 7:24:45 pm Pieter Donche wrote: > At the first install of a package via the ports collection (cd > /usr/ports/../..; make install clean), if the package provides > configuration options, you can check these on a menu screen, > or accept all the defaults. > > If later on, you want to know what the set of the options were when you > installed a port, how to find that out? I tried > # cd /usr/ports// > # make > hoping to see the menu again, but it doesn't show any menu, but says: > ===> Found saved configuration for > > Where is that saved configuration kept ?? Under /var/db/ports/.../ in a file named "options" [gonz...@inferna ~]% more /var/db/ports/hplip/options # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for hplip-2.8.2_2 _OPTIONS_READ=hplip-2.8.2_2 WITH_GUI=true [gonz...@inferna ~]% > How to get a menu displayed again so you can see and check the options > you want? "make config" or "make rmconfig" as the other posters told you, or just go ahead and manually delete rm -f the options file prior to the "make install clean" Regards -- Blessings Gonzalo Nemmi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Ports Options
Hello, On Fri, Feb 20, 2009 at 4:24 PM, Pieter Donche wrote: > At the first install of a package via the ports collection (cd > /usr/ports/../..; make install clean), if the package provides configuration > options, you can check these on a menu screen, > or accept all the defaults. > > If later on, you want to know what the set of the options were when you > installed a port, how to find that out? I tried > # cd /usr/ports// > # make > hoping to see the menu again, but it doesn't show any menu, but says: > ===> Found saved configuration for > > Where is that saved configuration kept ?? > How to get a menu displayed again so you can see and check the options > you want? "make config" will show you the menu with the port's options again. "make showconfig" will show you the previously saved configuration. "make rmconfig" will delete the saved configuration. Please refer to [1] for more information on how to use ports. Regards Rambius [1] http://www.freebsd.org/doc/en/books/handbook/ports-using.html -- Tangra Mega Rock: http://www.radiotangra.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Ports Options
Pieter Donche writes: > If later on, you want to know what the set of the options were when you > installed a port, how to find that out? I tried > # cd /usr/ports// > # make # make showconfig Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Ports Options
On Fri, Feb 20, 2009 at 4:24 PM, Pieter Donche wrote: > At the first install of a package via the ports collection (cd > /usr/ports/../..; make install clean), if the package provides configuration > options, you can check these on a menu screen, > or accept all the defaults. > > If later on, you want to know what the set of the options were when you > installed a port, how to find that out? I tried > # cd /usr/ports// > # make > hoping to see the menu again, but it doesn't show any menu, but says: > ===> Found saved configuration for > > Where is that saved configuration kept ?? > How to get a menu displayed again so you can see and check the options > you want? `make config' -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Ports Options
On Friday 20 February 2009 12:24:45 Pieter Donche wrote: > At the first install of a package via the ports collection (cd > /usr/ports/../..; make install clean), if the package provides > configuration options, you can check these on a menu screen, > or accept all the defaults. > > If later on, you want to know what the set of the options were when you > installed a port, how to find that out? I tried > # cd /usr/ports// > # make > hoping to see the menu again, but it doesn't show any menu, but says: > ===> Found saved configuration for > > Where is that saved configuration kept ?? > How to get a menu displayed again so you can see and check the options > you want? # cd /usr/ports// # make config Beech -- --- Beech Rintoul - FreeBSD Developer - be...@freebsd.org /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.1R/announce.html --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Ports Options
At the first install of a package via the ports collection (cd /usr/ports/../..; make install clean), if the package provides configuration options, you can check these on a menu screen, or accept all the defaults. If later on, you want to know what the set of the options were when you installed a port, how to find that out? I tried # cd /usr/ports// # make hoping to see the menu again, but it doesn't show any menu, but says: ===> Found saved configuration for Where is that saved configuration kept ?? How to get a menu displayed again so you can see and check the options you want? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: priority of make/ports options (?) -- FreeBSD Port: sysutils/portconf
Doug Barton wrote: > martinko wrote: >> Hello, >> >> I'm using portconf to set ports' knobs. Also I'm setting some general >> knobs via make.conf. >> >> Now I've run into this situation: >> - i've got WITH_GECKO=seamonkey in /etc/make.conf >> - yelp from new gnome 2.16 does not build with knob above. therefore in >> /usr/local/etc/ports.conf i set: >> x11/yelp: WITH_MAN | WITH_INFO | USE_GECKO=xulrunner >> Unfortunately it does not work as I intended -- when I `portinstall >> gnome2-lite` it tries to build yelp WITH_GECKO=seamonkey. :-/ >> >> How can I solve this pls ?? >> How can I specify a general knob and then override it for some ports ? > > Don't set global knobs in make.conf. Set them in ports.conf like this: > > *:WITH_GECKO=seamonkey > x11/yelp:WITH_MAN | WITH_INFO | USE_GECKO=xulrunner > > That should give you the precedence that you need. > > hth, > > Doug > Doug, thank you for the idea! Meanwhile, when I was going to check it, I found out that I mistyped (originally) my knob -- it should be WITH_GECKO=xulrunner (not USE_GECKO) -- and it works now, too! :-) Anyway, I'm going to move port related knobs from make.conf to ports.conf (which wasn't available at the time I populated my make.conf). With regards, Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: priority of make/ports options (?) -- FreeBSD Port: sysutils/portconf
martinko wrote: Hello, I'm using portconf to set ports' knobs. Also I'm setting some general knobs via make.conf. Now I've run into this situation: - i've got WITH_GECKO=seamonkey in /etc/make.conf - yelp from new gnome 2.16 does not build with knob above. therefore in /usr/local/etc/ports.conf i set: x11/yelp: WITH_MAN | WITH_INFO | USE_GECKO=xulrunner Unfortunately it does not work as I intended -- when I `portinstall gnome2-lite` it tries to build yelp WITH_GECKO=seamonkey. :-/ How can I solve this pls ?? How can I specify a general knob and then override it for some ports ? Don't set global knobs in make.conf. Set them in ports.conf like this: *: WITH_GECKO=seamonkey x11/yelp: WITH_MAN | WITH_INFO | USE_GECKO=xulrunner That should give you the precedence that you need. hth, Doug -- This .signature sanitized for your protection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
priority of make/ports options (?) -- FreeBSD Port: sysutils/portconf
Hello, I'm using portconf to set ports' knobs. Also I'm setting some general knobs via make.conf. Now I've run into this situation: - i've got WITH_GECKO=seamonkey in /etc/make.conf - yelp from new gnome 2.16 does not build with knob above. therefore in /usr/local/etc/ports.conf i set: x11/yelp: WITH_MAN | WITH_INFO | USE_GECKO=xulrunner Unfortunately it does not work as I intended -- when I `portinstall gnome2-lite` it tries to build yelp WITH_GECKO=seamonkey. :-/ How can I solve this pls ?? How can I specify a general knob and then override it for some ports ? Cheers, Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
