Bryan Drewery wrote
> 1. This should not happen if you have the latest portmaster port and use
> the PKGNGPATCH option.
> 2. It is not required that you use binary packages with pkgng. You can
> continue using ports with portmaster/portupgrade just fine.
> 3. Portmaster *is* fully ready for pkgng,
Lars Engels-2 wrote
> But for desktop applications port maintainers should create one:
> http://www.freebsd.org/doc/en/books/porters-handbook/book.html#desktop-entries
Corrrect, and hence my question.
It looks like the variable I was looking for is for sub-menu
placement. Thanks for the link Olvi
--- On Fri, 11/9/12, Bryan Drewery wrote:
> From: Bryan Drewery
> Subject: Re: pkgng woes
> To: "Jeffrey Bouquet"
> Cc: freebsd-ports@freebsd.org
> Date: Friday, November 9, 2012, 10:51 AM
> On 11/9/2012 12:42 PM, Jeffrey
> Bouquet wrote:
> >
> >
> > --- On Fri, 11/9/12, Anton Shterenlikht
--- On Fri, 11/9/12, Chris Rees wrote:
> From: Chris Rees
> Subject: Re: pkgng woes
> To: "Jeffrey Bouquet"
> Cc: "FreeBSD Mailing List" , "Beeblebrox"
>
> Date: Friday, November 9, 2012, 11:09 AM
> On 9 Nov 2012 18:34, "Jeffrey
> Bouquet"
> wrote:
> >
> >
> >
> > --- On Fri, 11/9/12, Chri
On Fri, Nov 09, 2012 at 06:43:22PM -0500, Eitan Adler wrote:
> On 9 November 2012 18:41, Baptiste Daroussin wrote:
> >> I prefer the latter.
> >
> > @Eitan
> > I do prefer the environnement variable because the users that are using
> > pkg_*
> > tools for some reason we can't imagine (there is al
On 9 November 2012 19:03, Baptiste Daroussin wrote:
> On Fri, Nov 02, 2012 at 09:53:45PM -0400, Adam McDougall wrote:
>> The mailing lists don't seem to be a good place to send bugs
>> and get attention, and I've found a few that I want to report
>> and have in a bug system somewhere. Should I us
On Fri, Nov 02, 2012 at 09:53:45PM -0400, Adam McDougall wrote:
> The mailing lists don't seem to be a good place to send bugs
> and get attention, and I've found a few that I want to report
> and have in a bug system somewhere. Should I use gnats? Thanks.
> __
I am sorry I made misunderstanding to this issue.
Once CC= is set when ruby is built, it seems that ruby
remembers this in lib/ruby/1.9/i386-freebsd9/rbconfig.rb
file. That is why generated Makefile from extconf.rb
always invokes the same compiler even if environmental
parameter is changed to oth
On 9 November 2012 18:43, Eitan Adler wrote:
> On 9 November 2012 18:41, Baptiste Daroussin wrote:
>>> I prefer the latter.
>>
>> @Eitan
>> I do prefer the environnement variable because the users that are using pkg_*
>> tools for some reason we can't imagine (there is always cases) can safely
>
On 9 November 2012 18:41, Baptiste Daroussin wrote:
>> I prefer the latter.
>
> @Eitan
> I do prefer the environnement variable because the users that are using pkg_*
> tools for some reason we can't imagine (there is always cases) can safely use
> it
> without this warning.
Okay. I'll send you
On Fri, Nov 09, 2012 at 04:10:43PM -0500, Eitan Adler wrote:
> On 9 November 2012 15:58, Alexander Leidinger wrote:
> > Hi,
> >
> > is this intended (current as of r242511)?
>
> Ah. I have a patch to partly fix this. I forgot that the conversion
> process itself uses the repo. The correct fix is
On Thu, Nov 8, 2012 at 8:12 AM, Bernhard Fröhlich wrote:
> On Wed, Nov 7, 2012 at 4:21 AM, Brandon Gooch
> wrote:
>> On Tue, Oct 30, 2012 at 2:16 AM, Bernhard Fröhlich wrote:
>>> Hi virtualbox users!
>>>
>>> This is again a call for testers to get some feedback before we commit
>>> VirtualBox 4.
On 9 November 2012 15:58, Alexander Leidinger wrote:
> Hi,
>
> is this intended (current as of r242511)?
Ah. I have a patch to partly fix this. I forgot that the conversion
process itself uses the repo. The correct fix is either to add an
override environment variable or to have the conversion wr
Hi,
is this intended (current as of r242511)?
---snip---
# pkg2ng
pkg_info: Don't use the pkg_ tools if you are using pkgng
Creating backup pkg_info(1) database directory in /var/db/pkg.bak.
pkg_info: Don't use the pkg_ tools if you are using pkgng
pkg_info: Don't use the pkg_ tools if you are usi
The last java/icedtea-web/Makefile update
http://www.freebsd.org/cgi/cvsweb.cgi/ports/java/icedtea-web/Makefile.diff?r1=1.24;r2=1.25;f=h
adds:
USE_GECKO= libxul
What for?
I have www/firefox installed including /usr/local/lib/firefox/libxul.so .
Why do I need now to build and install also www
On 9 Nov 2012 18:34, "Jeffrey Bouquet" wrote:
>
>
>
> --- On Fri, 11/9/12, Chris Rees wrote:
>
> > From: Chris Rees
> > Subject: Re: pkgng woes
> > To: "Beeblebrox"
> > Cc: freebsd-ports@freebsd.org
> > Date: Friday, November 9, 2012, 8:18 AM
> > On 9 Nov 2012 09:53, "Beeblebrox"
> >
> > wrote
On 11/9/2012 12:42 PM, Jeffrey Bouquet wrote:
>
>
> --- On Fri, 11/9/12, Anton Shterenlikht wrote:
>
>> From: Anton Shterenlikht
>> Subject: Re: pkgng woes
>> To: freebsd-ports@freebsd.org, zap...@berentweb.com
>> Date: Friday, November 9, 2012, 5:22 AM
>> @anton
>> portmaster --check-
--- On Fri, 11/9/12, Kimmo Paasiala wrote:
> From: Kimmo Paasiala
> Subject: Re: pkgng woes
> To: "Beeblebrox"
> Cc: freebsd-ports@freebsd.org
> Date: Friday, November 9, 2012, 4:54 AM
> On Fri, Nov 9, 2012 at 2:39 PM,
> Beeblebrox
> wrote:
> > @anton
> > portmaster --check-depends does not
--- On Fri, 11/9/12, Anton Shterenlikht wrote:
> From: Anton Shterenlikht
> Subject: Re: pkgng woes
> To: freebsd-ports@freebsd.org, zap...@berentweb.com
> Date: Friday, November 9, 2012, 5:22 AM
> @anton
> portmaster --check-depends does not work
> for me. Shows everything as fine
>
--- On Fri, 11/9/12, Chris Rees wrote:
> From: Chris Rees
> Subject: Re: pkgng woes
> To: "Beeblebrox"
> Cc: freebsd-ports@freebsd.org
> Date: Friday, November 9, 2012, 8:18 AM
> On 9 Nov 2012 09:53, "Beeblebrox"
>
> wrote:
> >
> > Pkgng, as a concept may be great, but it's not really
> work
I'm working on a new port (snorby), and it requires ruby. I've never built
a ruby-based port before and confess total ignorance of how ruby works and
how freebsd ports can use ruby to install software.
I've looked at the Porter's Handbook, but it's very little help. I've
pored over /usr/port
I'm trying to update one of my ports (security/afterglow). When I run make
depends `make -V PORTNAME`, the build fails on cairo because librsvg
doesn't exist.
So I go into the librsvg2 port and build it. But it fails because it needs
cairo.
Sweet. A genuine catch-22 situation.
Anyone hav
Hi,
Selecting RUBY_MODULE option for databases/rrdtool, and if you use
'clang' as the default compiler
by setting CC=clang at /etc/make.conf, this port would stop with the
following error message,
and any environmental setting like as USE_GCC=any could not affect.
gmake[4]: Leaving directory
`/us
On 11/8/2012 8:44 AM, portsc...@portscout.zi0r.com wrote:
> Dear port maintainer,
>
> The portscout new distfile checker has detected that one or more of your
> ports appears to be out of date. Please take the opportunity to check
> each of the ports listed below, and if possible and appropriate,
On Fri, Nov 09, 2012 at 01:49:22PM +, Olivier Duchateau wrote:
> 2012/11/9 Beeblebrox :
> > Some ports fail to create the launch icon (menu item) in the desktop menu.
> > To
> > correct this, one is to add in /usr/local/share/application a file by
> > .desktop like so:
> >
> > [Desktop Entry]
On 9 Nov 2012 09:53, "Beeblebrox" wrote:
>
> Pkgng, as a concept may be great, but it's not really working - at least
for
> me:
>
> 1. pkg2ng conversion does not do a complete job and I have about half of
my
> ports in purgatory or a quasi-installed state. The program runs and is
> installed but p
On 11/9/2012 6:32 AM, Beeblebrox wrote:
>
> - I did not realize that pkg2ng did not convert correctly, until portmaster
> started to try and install stuff that I knew was already on the system. Too
> late now. My db was probably problematic to start with
>
> I have not tried portmaster with pkgd
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
@anton
portmaster --check-depends does not work for me. Shows everything as
fine
but when I specifically target a port: *# portmaster -i graphics/gimp*
for
example, I get a long list of ports to be installed - meaning not all
of the
existing ports have be
On Fri, Nov 9, 2012 at 2:39 PM, Beeblebrox wrote:
> @anton
> portmaster --check-depends does not work for me. Shows everything as fine
> but when I specifically target a port: *# portmaster -i graphics/gimp* for
> example, I get a long list of ports to be installed - meaning not all of the
> exis
@anton
portmaster --check-depends does not work for me. Shows everything as fine
but when I specifically target a port: *# portmaster -i graphics/gimp* for
example, I get a long list of ports to be installed - meaning not all of the
existing ports have been registered correctly, hence --check depe
- I did not realize that pkg2ng did not convert correctly, until portmaster
started to try and install stuff that I knew was already on the system. Too
late now. My db was probably problematic to start with
I have not tried portmaster with pkgdb yet but I understand recent versions
of it support
> 2. I am used to portmaster and I accept that portupgrade is "more
ready" to
> be used with pkgng than portmaster. However, portmaster has the
> "--check-depends" option which I would normally use to correct
problem #1,
> alas I see no similar function in portupgr
Answering this in-line as a user of pkgng and binary packages:
On 11/9/2012 4:53 AM, Beeblebrox wrote:
Pkgng, as a concept may be great, but it's not really working - at least for
me:
1. pkg2ng conversion does not do a complete job and I have about half of my
ports in purgatory or a quasi-insta
*update:*
In pkgtools.conf, the IGNORE_CATEGORIES works and prevents unwanted ports
from being installed, while HOLD_PKGS does not work when using portupgrade
and I get my nemesis net/avahi-app installed anyway (whether I want it or
not).
--
View this message in context:
http://freebsd.1045724
I am snagged in graphics/opencv in my massive upgrade of ports, and see error
messages in the log file indicating errors in the C code. I also see there is
a newer version of openCV out. But I was able to pigeonhole graphics/opencv
and four other ports that depend on opencv and complete the rest
Some ports fail to create the launch icon (menu item) in the desktop menu. To
correct this, one is to add in /usr/local/share/application a file by
.desktop like so:
[Desktop Entry]
Encoding=UTF-8
Name=
GenericName=
Comment=
TryExec=
Exec=
Icon=
Type=Application
Categories=;;;
My question is: The
Pkgng, as a concept may be great, but it's not really working - at least for
me:
1. pkg2ng conversion does not do a complete job and I have about half of my
ports in purgatory or a quasi-installed state. The program runs and is
installed but pkgdb does not have a record for it. So my ports updates
38 matches
Mail list logo
