Using pkg(ng) in conjunction with the port ports/mgmt/portupgrade
results in long waiting cycles when portupgrade is updating the local
database, it is even on fast boxes sometimes in the range of a minute or
even two.
Is this usual or is there something wrong with my setup?
Regards,
Oliver
---
At least pkgng reports/detects it:
pkg: patch-2.7 conflicts with gettext-0.18.1.1 (installs files into the same
place). Problematic file: /usr/local/lib/charset.alias
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
files/Makefile.bsd has WARNS=3, but:
/usr/obj/ports/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ri_image/ptile.cpp:
In static member function 'static void PTile::FreeAncientBuffers(long int)':
/usr/obj/ports/usr/ports/graphics/libfpx/work/libfpx-1.3.1-1/ri_image/ptile.cpp:778:24:
error: variable
04.10.2012 17:47, Brett wrote:
Has Adobe possibly pulled permission for this to be distributed?
= Attempting to fetch
http://fpdownload.macromedia.com/get/flashplayer/pdc/11.1.102.55/install_flash_player_11_linux.i386.tar.gz
fetch:
04.10.2012 22:16, Jerry wrote:
Yes, it is a bit of a PITA isn't it. I wish flashplayer could be
replaced be something better that works on UNIX and all platforms for
that matter. Maybe HTML 5 will enable people to do without this crap.
This isn't a matter of replacing it, it is a matter of
Hi,
I want to propose and make the actual move of the WWW information from the
pkg-descr to the Makefile itself via a WWW variable.
doing this will have multiple benefits:
* consistency all metadata bug this one are in Makefile
* speedup make describe avoiding using grep to get the
On 02-10-2012 21:20, Shane Ambler wrote:
I found a situation where gcc v4.2 compiles a i386 working binary and
v4.6 doesn't. (Currently 4.7 and 4.8 fail to build this code) I have
verified that this happens with 8.2/8.3/9.0 i386 systems. x86_64
versions build without issue as does clang
On 5 October 2012 10:05, Baptiste Daroussin b...@freebsd.org wrote:
Hi,
I want to propose and make the actual move of the WWW information from the
pkg-descr to the Makefile itself via a WWW variable.
doing this will have multiple benefits:
* consistency all metadata bug this one are in
Le ven 5 oct 12 à 16:05:35 +0200, Baptiste Daroussin b...@freebsd.org
écrivait :
Hi,
Hello,
I want to propose and make the actual move of the WWW information from the
pkg-descr to the Makefile itself via a WWW variable.
Good idea!
But just a warning: some pkg-desc may contain two URLs.
Thierry Thomas wrote on 05.10.2012 18:36:
Le ven 5 oct 12 à 16:05:35 +0200, Baptiste Daroussin b...@freebsd.org
écrivait :
Hi,
Hello,
I want to propose and make the actual move of the WWW information from the
pkg-descr to the Makefile itself via a WWW variable.
Good idea!
But just a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/5/12 4:33 AM, Andriy Gapon wrote:
At least pkgng reports/detects it:
pkg: patch-2.7 conflicts with gettext-0.18.1.1 (installs files into
the same place). Problematic file: /usr/local/lib/charset.alias
Hi Andriy,
Thank you for the
On Fri, Oct 05, 2012 at 04:05:35PM +0200, Baptiste Daroussin wrote:
I want to propose and make the actual move of the WWW information from the
pkg-descr to the Makefile itself via a WWW variable.
doing this will have multiple benefits:
* consistency all metadata bug this one are in Makefile
On Fri, Oct 05, 2012 at 10:25:07AM -0400, Eitan Adler wrote:
On 5 October 2012 10:05, Baptiste Daroussin b...@freebsd.org wrote:
Hi,
I want to propose and make the actual move of the WWW information from the
pkg-descr to the Makefile itself via a WWW variable.
doing this will have
On Fri, Oct 05, 2012 at 06:41:28PM +0400, Ruslan Mahmatkhanov wrote:
Thierry Thomas wrote on 05.10.2012 18:36:
Le ven 5 oct 12 à 16:05:35 +0200, Baptiste Daroussin b...@freebsd.org
écrivait :
Hi,
Hello,
I want to propose and make the actual move of the WWW information from the
On Fri, Oct 05, 2012 at 04:15:44PM +0100, Shaun Amott wrote:
On Fri, Oct 05, 2012 at 04:05:35PM +0200, Baptiste Daroussin wrote:
I want to propose and make the actual move of the WWW information from the
pkg-descr to the Makefile itself via a WWW variable.
doing this will have multiple
On 10/5/2012 3:24 AM, O. Hartmann wrote:
Using pkg(ng) in conjunction with the port ports/mgmt/portupgrade
results in long waiting cycles when portupgrade is updating the local
database, it is even on fast boxes sometimes in the range of a minute or
even two.
You mean
Am 10/05/12 17:28, schrieb Bryan Drewery:
On 10/5/2012 3:24 AM, O. Hartmann wrote:
Using pkg(ng) in conjunction with the port ports/mgmt/portupgrade
results in long waiting cycles when portupgrade is updating the local
database, it is even on fast boxes sometimes in the range of a minute or
On 10/5/2012 10:40 AM, O. Hartmann wrote:
Am 10/05/12 17:28, schrieb Bryan Drewery:
On 10/5/2012 3:24 AM, O. Hartmann wrote:
Using pkg(ng) in conjunction with the port ports/mgmt/portupgrade
results in long waiting cycles when portupgrade is updating the local
database, it is even on fast
On 5 October 2012 11:17, Baptiste Daroussin b...@freebsd.org wrote:
While the idea sounds good, how do you retrive the informations out of a
simple
make command, and possibilty with limiting the parsing as much as possible?
equivalent of make -VWWW (for example for make describe)
I'm not
On Fri, 05 Oct 2012 10:47:33 -0500
Bryan Drewery br...@shatow.net wrote:
On 10/5/2012 10:40 AM, O. Hartmann wrote:
Am 10/05/12 17:28, schrieb Bryan Drewery:
On 10/5/2012 3:24 AM, O. Hartmann wrote:
Using pkg(ng) in conjunction with the port ports/mgmt/portupgrade
results in long
How about storing this metada in a YAML-encoded file? The Ruby people use
YAML for lots of things. libyaml is MIT licensed.
Jos
On Oct 5, 2012 8:33 AM, Baptiste Daroussin b...@freebsd.org wrote:
On Fri, Oct 05, 2012 at 04:15:44PM +0100, Shaun Amott wrote:
On Fri, Oct 05, 2012 at 04:05:35PM
On 5 October 2012 12:08, Jos Backus j...@catnook.com wrote:
How about storing this metada in a YAML-encoded file? The Ruby people use
YAML for lots of things. libyaml is MIT licensed.
No objections per se to this. I do believe there were some concerns
about increasing the number of inodes the
On Fri, Oct 5, 2012 at 9:18 AM, Eitan Adler li...@eitanadler.com wrote:
On 5 October 2012 12:08, Jos Backus j...@catnook.com wrote:
How about storing this metada in a YAML-encoded file? The Ruby people use
YAML for lots of things. libyaml is MIT licensed.
No objections per se to this. I do
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/5/12 4:33 AM, Andriy Gapon wrote:
At least pkgng reports/detects it:
pkg: patch-2.7 conflicts with gettext-0.18.1.1 (installs files into
the same place). Problematic file: /usr/local/lib/charset.alias
Hello Andriy,
I just committed
On Fri, Oct 05, 2012 at 09:08:52AM -0700, Jos Backus wrote:
How about storing this metada in a YAML-encoded file? The Ruby people use
YAML for lots of things. libyaml is MIT licensed.
Jos
pkgng uses libyaml for its manifest :)
converting to yaml will be a more complicated work and will need
on 05/10/2012 19:28 Greg Larkin said the following:
On 10/5/12 4:33 AM, Andriy Gapon wrote:
At least pkgng reports/detects it:
pkg: patch-2.7 conflicts with gettext-0.18.1.1 (installs files into
the same place). Problematic file: /usr/local/lib/charset.alias
Hello Andriy,
I just
On 23/09/2012 18:36, Christopher Dawkins wrote:
I am sorry to bring this to your attention: you all do a lot of work
that considerably benefits me and many others.
But I cannot compile kdenetwork-4.8.4_2 because it seems to need libotr3.
The advice in 20120908 seems irrelevant because
On Fri, Oct 05, 2012 at 05:32:21PM +0200, Baptiste Daroussin wrote:
On Fri, Oct 05, 2012 at 04:15:44PM +0100, Shaun Amott wrote:
On Fri, Oct 05, 2012 at 04:05:35PM +0200, Baptiste Daroussin wrote:
I want to propose and make the actual move of the WWW information from the
pkg-descr to the
On Fri, Oct 05, 2012 at 11:04:07PM +0100, Shaun Amott wrote:
On Fri, Oct 05, 2012 at 05:32:21PM +0200, Baptiste Daroussin wrote:
On Fri, Oct 05, 2012 at 04:15:44PM +0100, Shaun Amott wrote:
On Fri, Oct 05, 2012 at 04:05:35PM +0200, Baptiste Daroussin wrote:
I want to propose and make the
Hi,
There are still 1590 ports to be converted, more than 1600 has already been
converted, please consider converting yours.
Here is a list of ports to be converted:
http://wiki.freebsd.org/Ports/Options/ConvertingToOptionsNG
Here is the list of maintainers having ports to be converted:
On 10/05/2012 07:05 AM, Baptiste Daroussin wrote:
Hi,
I want to propose and make the actual move of the WWW information from the
pkg-descr to the Makefile itself via a WWW variable.
doing this will have multiple benefits:
* consistency all metadata bug this one are in Makefile
...
I'm working on updating the barnyard2 port, and I'm changing the port to
use the new OPTIONS structure. It seems no matter what I do, the first
port OPTION is automatically selected.
I've tried OPTIONS_DEFAULT=, OPTIONS_DEFAULT= none, and not using
OPTIONS_DEFAULT at all. I do not want the
Good day, ports!
Something that I have noticed in the world of home desktops although *BSD
is total server package and I can do many things.
The StEam platform from ValVe corp is a large step in gaming at this point.
I have a 13 year old who has a slew of friends on this gaming
Hello,
I had a small discussion with friends about this topic at work. But...
comes out that are few linux games that runs on steam. Maybe the only big
sensation will be the left4dead that is coming with the plataform release.
Not saying that is not worth to port it... But about the games your
Good day, ports!
A new port request that is probably critical to moving forward with a total
collaborative service I don't see Zimbra anywhere.
Could you please check into this and see what the possibility is?
Thank you,
Paul Pathiakis
Atlantis Services
Owner
Paul Pathiakis pathia...@yahoo.com wrote:
The StEam platform from ValVe corp is a large step in gaming at
this point ... StEam is in the process of moving over to Linux.
Please don't fall behind in the effort of bringing this platform
to BSD.
Had you considered trying to run their Linux
I just converted a port over to the new options structure and have a few
observations. I have not been involved in any of the discussions about the
structure as I didn't have the time to get involved. However, a couple things
came to mind during the process:
1. The Port handbook is actually
On Fri, Oct 5, 2012 at 8:52 PM, Paul Schmehl pschmehl_li...@tx.rr.comwrote:
I'm working on updating the barnyard2 port, and I'm changing the port to
use the new OPTIONS structure. It seems no matter what I do, the first
port OPTION is automatically selected.
I've tried OPTIONS_DEFAULT=,
On Friday, October 05, 2012 22:52:05 Paul Schmehl wrote:
I'm working on updating the barnyard2 port, and I'm changing the port to
use the new OPTIONS structure. It seems no matter what I do, the first
port OPTION is automatically selected.
I've tried OPTIONS_DEFAULT=, OPTIONS_DEFAULT= none,
--On October 5, 2012 10:52:05 PM -0500 Paul Schmehl
pschmehl_li...@tx.rr.com wrote:
I'm working on updating the barnyard2 port, and I'm changing the port to
use the new OPTIONS structure. It seems no matter what I do, the first
port OPTION is automatically selected.
I've tried
On Friday, October 05, 2012 22:07:40 Jason Helfman wrote:
OPTIONS_SET= OPTION1 OPTION2
That should be OPTIONS_DEFINE= OPTION1 OPTION2
OPTIONS_SET should only be used in /etc/make.conf to set global options.
- Jason
___
freebsd-ports@freebsd.org
On Fri, Oct 5, 2012 at 10:19 PM, Jason E. Hale jh...@freebsd.org wrote:
On Friday, October 05, 2012 22:07:40 Jason Helfman wrote:
OPTIONS_SET= OPTION1 OPTION2
That should be OPTIONS_DEFINE= OPTION1 OPTION2
OPTIONS_SET should only be used in /etc/make.conf to set global options.
- Jason
42 matches
Mail list logo
