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
-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
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 l
re 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,
> > > ===> 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
&
> ===> 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
df
> ===> 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
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 t
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.
>
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
___
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
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,
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
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
___
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
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, yo
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
install
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 abo
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.con
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:
20 matches
Mail list logo
