There is pkg2ng tool. I think reverse tool could be useful for such
scenario:
1. System packages managed by pkgng
2. pkgng2pkg creates /var/db/pkg structure, for read-only tasks
3. Any soft relying on get info from /var/db/pkg still works (partially,
because of RO).
And then one could learn new
If you are interested in eaccelerator with php 5.4, please try the
following patch and report success/failure.
http://www.alexdupre.com/eaccelerator.diff
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
On Wed, Aug 22, 2012 at 05:37:54AM -0700, Jeffrey Bouquet wrote:
I view, rightly-or-wrongly, the mandatory usage of pkgng VS
/var/db/pkg/portname-number, as somewhat of a showstopper, at least
without more assurances... I interact daily with /var/db/pkg as
follows...
using the shells'
On 23 August 2012 10:21, Christer Solskogen
christer.solsko...@gmail.com wrote:
how do you regenerate this file these days? make index seems to take a
pretty long time.
It's a pretty big file :)
Try make fetchindex.
Chris
___
From owner-freebsd-po...@freebsd.org Thu Aug 23 10:29:18 2012
how do you regenerate this file these days? make index seems to take a
pretty long time.
I prefer fetchindex
Anton
___
freebsd-ports@freebsd.org mailing list
On Thu, Aug 23, 2012 at 11:21:24AM +0200 I heard the voice of
Christer Solskogen, and lo! it spake thus:
how do you regenerate this file these days? make index seems to take
a pretty long time.
I switch to using portsnap years back, which provides it prebuilt. I
prefer that to fetchindex,
I am following with dread the planned implementation of the deprecation of
/var/db/pkg as a package registry... I use each /var/db/pkg directory as a
database into the port installation/status, using
sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff.
For instance, an
Florent Thoumie, aka flz@, recently stepped down from his roll on the
FreeBSD Ports Management team.
Florent started on portmgr back in August 2008, being instrumental in
maintaining the legacy pkg_* code plus other aspects of the ports
infrastructure, including but not limited to the unifying of
On 08/23/2012 12:26, Jeffrey Bouquet wrote:
I am following with dread the planned implementation of the deprecation of
/var/db/pkg as a package registry... I use each /var/db/pkg directory as a
database into the port installation/status, using
sed/grep/portmaster/portmanager/.sh
On 23 Aug 2012 17:50, Kris Moore k...@pcbsd.org wrote:
On 08/23/2012 12:26, Jeffrey Bouquet wrote:
I am following with dread the planned implementation of the deprecation
of /var/db/pkg as a package registry... I use each /var/db/pkg directory as
a database into the port installation/status,
--On August 23, 2012 4:28:20 PM + Thomas Abthorpe
portmgr-secret...@freebsd.org wrote:
Florent Thoumie, aka flz@, recently stepped down from his roll on the
FreeBSD Ports Management team.
Florent, thank you for your service, your hard work and your dedication to
FreeBSD.
--
Paul
On 8/23/2012 6:26 PM, Jeffrey Bouquet wrote:
I am following with dread the planned implementation of the deprecation of
/var/db/pkg as a package registry... I use each /var/db/pkg directory as a
database into the port installation/status, using
sed/grep/portmaster/portmanager/.sh
On 08/23/2012 13:10, Jeremy Messenger wrote:
On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore k...@pcbsd.org wrote:
On 08/23/2012 12:26, Jeffrey Bouquet wrote:
I am following with dread the planned implementation of the deprecation of
/var/db/pkg as a package registry... I use each /var/db/pkg
On 23 August 2012 20:50, Kris Moore k...@pcbsd.org wrote:
On 08/23/2012 13:10, Jeremy Messenger wrote:
On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore k...@pcbsd.org wrote:
On 08/23/2012 12:26, Jeffrey Bouquet wrote:
I am following with dread the planned implementation of the deprecation of
On 23/08/2012 20:50, Kris Moore wrote:
Well, it was about time I got to doing a benchmark of this anyway :)
I did quick benchmark of how one of our utilities parses through a list
of 1k packages on a newer i5 system:
First test, using /var/db/pkg/pkg check we have been doing:
0.178s
On Thu, Aug 23, 2012 at 03:50:11PM -0400, Kris Moore wrote:
On 08/23/2012 13:10, Jeremy Messenger wrote:
On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore k...@pcbsd.org wrote:
On 08/23/2012 12:26, Jeffrey Bouquet wrote:
I am following with dread the planned implementation of the deprecation
On 2012-08-23 21:50, Kris Moore wrote:
On 08/23/2012 13:10, Jeremy Messenger wrote:
On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore k...@pcbsd.org wrote:
On 08/23/2012 12:26, Jeffrey Bouquet wrote:
I am following with dread the planned implementation of the deprecation of
/var/db/pkg as a
Just the patch I was looking for.
- Original Message -
FYI-
The mail/spamass-milter port won't build if the sendmail-sasl port
has
been built. The patch below fixes this.
The port maintainer is on the Cc. No bug has been reported.
Curtis
--- Makefile.orig
On 08/23/2012 16:31, olli hauer wrote:
On 2012-08-23 21:50, Kris Moore wrote:
On 08/23/2012 13:10, Jeremy Messenger wrote:
On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore k...@pcbsd.org wrote:
On 08/23/2012 12:26, Jeffrey Bouquet wrote:
I am following with dread the planned implementation of the
Hm, it's sqlite, so if the tables are indexed correctly, that should
be a quick query?
Or is it recursing through each dependency and listing that too?
adrian
___
freebsd-ports@freebsd.org mailing list
On 23 August 2012 21:37, Lawrence K. Chen, P.Eng. lkc...@ksu.edu wrote:
Just the patch I was looking for.
- Original Message -
FYI-
The mail/spamass-milter port won't build if the sendmail-sasl port
has
been built. The patch below fixes this.
The port maintainer is on the Cc.
On Thu, Aug 23, 2012 at 03:50:11PM -0400, Kris Moore wrote:
Well, it was about time I got to doing a benchmark of this anyway :)
I did quick benchmark of how one of our utilities parses through a list
of 1k packages on a newer i5 system:
First test, using /var/db/pkg/pkg check we have been
Hi,
It seems to me that renaming the pkg binary in /usr/sbin/pkg to
/usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is
confusing that running the command gets different results the second time it is
run vs. the first time. I can imagine a user saying I ran pkg, but it
On Thu, Aug 23, 2012 at 06:19:57PM -0400, Steve Wills wrote:
Hi,
It seems to me that renaming the pkg binary in /usr/sbin/pkg to
/usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is
confusing that running the command gets different results the second time it
is run vs.
On 8/23/2012 3:19 PM, Steve Wills wrote:
Hi,
It seems to me that renaming the pkg binary in /usr/sbin/pkg to
/usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is
confusing that running the command gets different results the second time it
is run vs. the first time. I
On 8/23/2012 5:19 PM, Steve Wills wrote:
Hi,
It seems to me that renaming the pkg binary in /usr/sbin/pkg to
/usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is
confusing that running the command gets different results the second time it
is run vs. the first time. I
Le Fri, 24 Aug 2012 00:27:13 +0200,
Baptiste Daroussin b...@freebsd.org a écrit :
Hello,
So, opinions? There may still be time to fix it for 9.1 if we can
decide quickly.
I do personnally have no opinion on this, I have hesitated long
between both before choosing /usr/sbin/pkg.
I'm
With the help of Alexander Motin, I have now started limited package
builds on the Arm architecture.
Right now builds are only being done for a few hand-selected ports, and
only on arm-9 with pkgng. No builds with the old pkg_* tools are
intended at this time.
For those of you with Arm systems,
On Thu, 23 Aug 2012 18:19:57 -0400
Steve Wills swi...@freebsd.org wrote:
Hi,
It seems to me that renaming the pkg binary in /usr/sbin/pkg
to /usr/sbin/pkg-bootstrap would make sense. From a user standpoint,
it is confusing that running the command gets different results the
second time it
On 23 August 2012 18:19, Steve Wills swi...@freebsd.org wrote:
Hi,
It seems to me that renaming the pkg binary in /usr/sbin/pkg to
/usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is
confusing that running the command gets different results the second time it
is run
On Aug 23, 2012, at 9:57 PM, Eitan Adler wrote:
On 23 August 2012 18:19, Steve Wills swi...@freebsd.org wrote:
Hi,
It seems to me that renaming the pkg binary in /usr/sbin/pkg to
/usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is
confusing that running the command
On 23 August 2012 22:05, Steve Wills swi...@freebsd.org wrote:
Why can't one of those steps be to run pkg-bootstrap?
Because the how-to may not be for a new system ;)
--
Eitan Adler
___
freebsd-ports@freebsd.org mailing list
On Aug 23, 2012, at 10:08 PM, Eitan Adler wrote:
On 23 August 2012 22:05, Steve Wills swi...@freebsd.org wrote:
Why can't one of those steps be to run pkg-bootstrap?
Because the how-to may not be for a new system ;)
The possibility of bad docs somewhere outside of our control, when we can
On 23 August 2012 22:15, Steve Wills swi...@freebsd.org wrote:
On Aug 23, 2012, at 10:08 PM, Eitan Adler wrote:
On 23 August 2012 22:05, Steve Wills swi...@freebsd.org wrote:
Why can't one of those steps be to run pkg-bootstrap?
Because the how-to may not be for a new system ;)
The
On Aug 23, 2012, at 10:23 PM, Eitan Adler wrote:
On 23 August 2012 22:15, Steve Wills swi...@freebsd.org wrote:
On Aug 23, 2012, at 10:08 PM, Eitan Adler wrote:
On 23 August 2012 22:05, Steve Wills swi...@freebsd.org wrote:
Why can't one of those steps be to run pkg-bootstrap?
Because
On 8/23/2012 7:23 PM, Eitan Adler wrote:
On 23 August 2012 22:15, Steve Wills swi...@freebsd.org wrote:
On Aug 23, 2012, at 10:08 PM, Eitan Adler wrote:
On 23 August 2012 22:05, Steve Wills swi...@freebsd.org wrote:
Why can't one of those steps be to run pkg-bootstrap?
Because the how-to
On 23 August 2012 22:55, Steve Wills swi...@freebsd.org wrote:
As far as I understand it, POLA is about changing existing things:
okay, so forget POLA. My point is that a user following a how to or
even *our* documentation on how to install something unrelated, like
say, apache, will be very
On 23 August 2012 22:59, Doug Barton do...@freebsd.org wrote:
No, POLA refers to not changing long-established practices out from
under the user.
forget pola
I tend to agree with Steve here ... we can't be responsible for other
people's poorly written docs.
This isn't about poorly written
On Thu, 23 Aug 2012, Eitan Adler wrote:
On 23 August 2012 22:55, Steve Wills swi...@freebsd.org wrote:
As far as I understand it, POLA is about changing existing things:
okay, so forget POLA. My point is that a user following a how to or
even *our* documentation on how to install something
39 matches
Mail list logo
