On Sun, Jun 03, 2012 at 11:54:06PM +0200, Baptiste Daroussin wrote:
You found a nice bug.
The options file is read the thing is that the UNIQUENAME is changed is
py-py-stl when the optionsfile is read and it is py27-py-stl when it is
written.
I don't know why yet, I'll fix it
[Please cc me, since I'm not subscribed to this list. I originally asked this
on questions@.]
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
On Sun, Jun 03, 2012 at 09:20:23PM +0200, Roland Smith wrote:
[Please cc me, since I'm not subscribed to this list. I originally asked this
on questions@.]
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
On Sun, Jun 03, 2012 at 09:20:23PM +0200, Roland Smith wrote:
[Please cc me, since I'm not subscribed to this list. I originally asked this
on questions@.]
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
On Sun, Jun 03, 2012 at 10:01:01PM +0200, Baptiste Daroussin wrote:
On Sun, Jun 03, 2012 at 09:20:23PM +0200, Roland Smith wrote:
[Please cc me, since I'm not subscribed to this list. I originally asked
this
on questions@.]
Hi,
With the release of the new options framework for
On 6/3/12 5:54 PM, Baptiste Daroussin wrote:
The real fix which will be long term, any volunteer? would be to define a
PKGNAMEEXTRAPREFIX in bsd.port.mk that bsd.*.mk can overwrite and create a
UNIQUENAME that is independant from that EXTRAPREFIX.
or back all this out until its actually
On 4-6-2012 0:20, Michael Scheidell wrote:
optionsng should have been 100% upward compatible. you should not be
forced to an an emergency update of a port you maintain just because the
ports tree broke things.
This has always been broken. It's just exposed by Roland cause he's
/adding/ an
