On 30/08/2012 22:44, John Nielsen wrote:
> After dialog(1) exits the script has a list of packages to mark as
> automatic. Is there a non-SQL way to efficiently get the inverse?
> I.e. the set { all_packages - new_automatic_package_list } ?
Use pkg query - it is really quite powerful. This shows
On Thu, Aug 30, 2012 at 04:09:00PM -0400, Steven Kreuzer wrote:
> >
> > So without further ado, this is what we would like to see at the top of
> > the makefile
> >
> > #
> > # $FreeBSD$
> > #
> >
> > PORTNAME=
> >
> > It is as easy as that :)
>
> This would make me happy. Another option I would
On Thu, Aug 30, 2012 at 12:54:17PM -1000, Doug Barton wrote:
> On 08/30/2012 09:56 AM, Thomas Abthorpe wrote:
> > So without further ado, this is what we would like to see at the top of
> > the makefile
> >
> > #
> > # $FreeBSD$
> > #
> >
> > PORTNAME=
> >
> > It is as easy as that :)
>
> I was
On 08/30/2012 07:32 AM, John Baldwin wrote:
> On Thursday, August 30, 2012 1:10:24 pm Chris Rees wrote:
>> On 30 Aug 2012 18:03, "John Baldwin" wrote:
>>>
>>> On Thursday, August 30, 2012 10:39:17 am Tijl Coosemans wrote:
On 27-08-2012 18:24, John Baldwin wrote:
> On Sunday, August 26, 20
On Aug 30, 2012, at 4:40 PM, Baptiste Daroussin wrote:
> Thanks you should be enough, can you provide a git format-patch patch so that
> you get your name in the logs :D
Here you go.
0001-Add-script-to-interactively-set-un-set-automatic-sta.patch
Description: Binary data
___
On 08/30/2012 10:09 AM, Steven Kreuzer wrote:
> This would make me happy. Another option I would like to throw out there is
> to just stick the # $FreeBSD$ at the end of the file so the first line
> is PORTNAME=
... also a good suggestion, and further improves the amount of usable
data when you fi
On 08/30/2012 09:56 AM, Thomas Abthorpe wrote:
> So without further ado, this is what we would like to see at the top of
> the makefile
>
> #
> # $FreeBSD$
> #
>
> PORTNAME=
>
> It is as easy as that :)
I was sort of afraid that would be the answer ... while I realize we
have massive historical
On Thu, Aug 30, 2012 at 04:33:09PM -0600, John Nielsen wrote:
> On Aug 30, 2012, at 3:28 PM, Baptiste Daroussin wrote:
>
> > On Thu, Aug 30, 2012 at 03:19:59PM -0600, John Nielsen wrote:
> >> I today noticed the "pkg autoremove" command for the first time, which
> >> does much the same thing as
On Aug 30, 2012, at 3:28 PM, Baptiste Daroussin wrote:
> On Thu, Aug 30, 2012 at 03:19:59PM -0600, John Nielsen wrote:
>> I today noticed the "pkg autoremove" command for the first time, which does
>> much the same thing as pkg_cutleaves but relies on the "automatic" flag in
>> the pkgng databa
On Aug 30, 2012, at 3:29 PM, Julien Laffaye wrote:
> On 8/30/2012 11:19 PM, John Nielsen wrote:
>> I today noticed the "pkg autoremove" command for the first time, which does
>> much the same thing as pkg_cutleaves but relies on the "automatic" flag in
>> the pkgng database rather than user inp
On Thu, Aug 30, 2012 at 11:29:14PM +0200, Julien Laffaye wrote:
> On 8/30/2012 11:19 PM, John Nielsen wrote:
> > I today noticed the "pkg autoremove" command for the first time, which does
> > much the same thing as pkg_cutleaves but relies on the "automatic" flag in
> > the pkgng database rather
On 8/30/2012 11:19 PM, John Nielsen wrote:
I today noticed the "pkg autoremove" command for the first time, which does much the same thing as
pkg_cutleaves but relies on the "automatic" flag in the pkgng database rather than user input to
determine which "leaf" ports can be removed. Unfortunate
Thank you,
Would you mind adding create a patch against the git tree of pkgng so that we
can include your script into the scripts subdirectory, so that we provide your
script along with the next pkg 1.0.1 as a contributed script?
regards,
Bapt
On Thu, Aug 30, 2012 at 03:19:59PM -0600, John Niels
I today noticed the "pkg autoremove" command for the first time, which does
much the same thing as pkg_cutleaves but relies on the "automatic" flag in the
pkgng database rather than user input to determine which "leaf" ports can be
removed. Unfortunately, the pkg2ng utility has no way of knowing
On Thu, Aug 30, 2012 at 3:56 PM, Thomas Abthorpe wrote:
> On Sun, Aug 26, 2012 at 02:02:47PM -0700, Doug Barton wrote:
>> The old Makefile headers, ala:
>>
>> # New ports collection makefile for:BIND 9.9.x
>> # Date created: 27 January 2012
>> # Whom:
On Sun, Aug 26, 2012 at 02:02:47PM -0700, Doug Barton wrote:
> The old Makefile headers, ala:
>
> # New ports collection makefile for:BIND 9.9.x
> # Date created: 27 January 2012
> # Whom: dougb
> #
> # $FreeBSD: head/dns/bind99/Makefile
On Aug 30, 2012, at 10:06 AM, Olivier Smedts wrote:
> 2012/8/30 John Nielsen :
>> Running ps in another terminal shows "pkg query %n-%v". Since the actual pkg
>> is now gone, I suspect this is really /usr/sbin/pkg. I further suspect that
>> it's waiting for y/n input (whether to install the bin
On 8/30/2012 10:43 AM, John Nielsen wrote:
> Thanks to everyone involved.
>
> I've been lightly testing pkg for a little while, but I still mainly use
> ports. This announcement prompted me to switch from portupgrade to
> portupgrade-devel (20120827 version) to see how it works with PKGNG. I
>
2012/8/30 John Nielsen :
> Running ps in another terminal shows "pkg query %n-%v". Since the actual pkg
> is now gone, I suspect this is really /usr/sbin/pkg. I further suspect that
> it's waiting for y/n input (whether to install the binary pkg) on its
> nonexistent stdin somewhere. I killed it
On Aug 30, 2012, at 9:43 AM, John Nielsen wrote:
> Thanks to everyone involved.
>
> I've been lightly testing pkg for a little while, but I still mainly use
> ports. This announcement prompted me to switch from portupgrade to
> portupgrade-devel (20120827 version) to see how it works with PKGN
On Thu, 30 Aug 2012 09:44:42 -0500, Matt Burke
wrote:
On 08/30/12 13:01, Mark Felder wrote:
I think you're very confused about what pkgng is for. At this time,
ports
are STILL the recommended way to install things and keep them up to
date.
Really? I think the last time I compiled X or a
Thanks to everyone involved.
I've been lightly testing pkg for a little while, but I still mainly use ports.
This announcement prompted me to switch from portupgrade to portupgrade-devel
(20120827 version) to see how it works with PKGNG. I encountered a couple
issues:
Portupgrade doesn't remov
[ Bryan Drewery wrote on Thu 30.Aug'12 at 9:51:55 -0500 ]
> On 8/30/2012 8:43 AM, Jamie Paul Griffin wrote:
> > [ Mark Felder wrote on Thu 30.Aug'12 at 7:01:43 -0500 ]
> >
> >> I think you're very confused about what pkgng is for. At this time, ports
> >> are STILL the recommended way to inst
On 8/30/2012 8:43 AM, Jamie Paul Griffin wrote:
> [ Mark Felder wrote on Thu 30.Aug'12 at 7:01:43 -0500 ]
>
>> I think you're very confused about what pkgng is for. At this time, ports
>> are STILL the recommended way to install things and keep them up to date.
>> Pkgng is the first step requ
On Thu, 30 Aug 2012 08:43:54 -0500, Jamie Paul Griffin
wrote:
Can i ask, why is it that shifting the community to using packages is
deemed to be a better approach? I like being able to select
configuration options to build software. I have never installed a
pre-compiled package since usi
On 08/30/12 13:01, Mark Felder wrote:
> I think you're very confused about what pkgng is for. At this time, ports
> are STILL the recommended way to install things and keep them up to date.
Really? I think the last time I compiled X or a web browser (until using
poudriere) was about 10 years ago.
Hi all,
Since Julien Laffaye and I started pkgng lots of things has happened and here we
are now.
After 2 years of development (first commit "Tue Sep 7 2010"), more than 2000
commits, 43 different contibutors. The pkgng team is proud to release pkg-1.0!
Before going further I would like to than
[ Mark Felder wrote on Thu 30.Aug'12 at 7:01:43 -0500 ]
> I think you're very confused about what pkgng is for. At this time, ports
> are STILL the recommended way to install things and keep them up to date.
> Pkgng is the first step required for us to get a better package management
> syst
I think you're very confused about what pkgng is for. At this time, ports
are STILL the recommended way to install things and keep them up to date.
Pkgng is the first step required for us to get a better package management
system so we can shift the community towards primarily using packages.
1. How do I get pkg to use packages built against 9.1-RC1? VirtualBox is
playing up (no ethernet, unkillable crashes, etc) and I suspect it's the
kernel module...
2. Is there a list of ports like nvidia-driver, nspluginwrapper,
linux-f10-flashplugin, sampleicc (dependency of libreoffice!) which ar
Greetings.
This port missing php5-simplexml dependency. Without it "Import" dont work.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd
31 matches
Mail list logo
