-Original Message-
From: Robert Huff
OK, Obi-wan - what's the replacement for:
a) "portsclean" with the C, D (single and double), and L
options? (Use no more than two commands.)
b) "pkg_sort" ?
With these, I will cheerfully delete portupgrade.
portupgrade != pkg_old
Actually, fo
On Sat, 05 Apr 2014 07:55:48 -0400
Robert Huff wrote:
> Matthew Seaman writes:
>
> > pkg(8) does a damn sight more than the old pkg_tools.
>
> Granted, though much of it I currently have little use
> for. :-)
>
> >> "pkgng" can do almost everything the old system can, and does it
>
Matthew Seaman writes:
> pkg(8) does a damn sight more than the old pkg_tools.
Granted, though much of it I currently have little use for. :-)
>> "pkgng" can do almost everything the old system can, and does it
>> better.>
>
> s/almost//
OK, Obi-wan - what's the replacemen
On 05/04/2014 00:44, sindrome wrote:
> foo:109:/home/foobar# pkg_version -v |grep needs it shows 240 ports that need
> updating.
It shows that you have out-of-date data in the remains of the old-style
/var/db/pkg that pkg2ng leaves in place.
Please execute the following command to clean up /var/
On 04/04/2014 23:49, Robert Huff wrote:
> "pkgng" can do almost everything the old system can, and does it
> better.
s/almost//
pkg(8) does a damn sight more than the old pkg_tools.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpke
On 04/04/2014 23:02, sindrome wrote:
> So I still keep my source, ports and docs in sync via svn update. Here's
> where the issue comes in. After I have done the pkg upgrade and it tells me
> all is up-to-date, the 'pkg_version -v |grep needs' command shows me dozens
> of ports that are not up-to
On Fri, 4 Apr 2014, Sindrome wrote:
On Apr 4, 2014, at 11:09 PM, Warren Block wrote:
On Fri, 4 Apr 2014, sindrome wrote:
From: Warren Block [mailto:wbl...@wonkity.com]
On Fri, 4 Apr 2014, sindrome wrote:
There is a major inconsistency with what pkg_version -v says is
outdated and what pkgng s
On Fri, 4 Apr 2014, sindrome wrote:
From: Warren Block [mailto:wbl...@wonkity.com]
Sent: Friday, April 04, 2014 9:23 PM
To: sindrome
Cc: 'Robert Huff'; po...@freebsd.org
Subject: RE: pkgng vs. portupgrade reporting ports outdated
On Fri, 4 Apr 2014, sindrome wrote:
There
PM
>> To: sindrome
>> Cc: 'Robert Huff'; po...@freebsd.org
>> Subject: RE: pkgng vs. portupgrade reporting ports outdated
>>
>>> On Fri, 4 Apr 2014, sindrome wrote:
>>>
>>> There is a major inconsistency with what pkg_version -v says i
mailto:wbl...@wonkity.com]
Sent: Friday, April 04, 2014 9:23 PM
To: sindrome
Cc: 'Robert Huff'; po...@freebsd.org
Subject: RE: pkgng vs. portupgrade reporting ports outdated
On Fri, 4 Apr 2014, sindrome wrote:
> There is a major inconsistency with what pkg_version -v says is
>
On Fri, 4 Apr 2014, sindrome wrote:
There is a major inconsistency with what pkg_version -v says is
outdated and what pkgng says.
Of course. pkg_version looks at the text files in /var/db/pkg, while
pkg looks at the database local.sqlite in that directory. The first
step in using pkg is ru
On Fri, Apr 4, 2014 at 4:44 PM, sindrome wrote:
> Here's more information
>
> foo:107:/home/foobar# pkg update
> Updating repository catalogue
>
> foo:108:/home/foobar# pkg upgrade
> Updating repository catalogue
> Nothing to do
>
> Now when I do a 'pkg_version -v|grep needs' I have
>
pkg_* tool
-Original Message-
From: sindrome [mailto:sindr...@gmail.com]
Sent: Friday, April 04, 2014 6:37 PM
To: 'Robert Huff'
Cc: po...@freebsd.org
Subject: RE: pkgng vs. portupgrade reporting ports outdated
It is my understanding it is generally a bad idea to mix the ol
It is my understanding it is generally a bad idea to mix the old and
new package systems. (It can be done, but it's beyond my pay grade and if
you're asking this I'd guess it is - at the moment - beyond yours.) "pkgng" can
do almost everything the old system can, and does it better.
"sindrome"
> With pkgng I issue a 'pkg update' followed by a 'pkg upgrade' and it
> shows me x number of ports that need to be updated. So it updates
> and completes just fine and of course it's much faster than building
> from source.
>
> So I still keep my source, ports and docs in syn
I'm a bit confused so I figured to see if someone can help me understand the
new pkgng system better. Before using it, I have always done a cvs update
(now svn update) to the ports tree and I would do a simple 'pkg_version
-v|grep needs' to see what ports were out-of-date and then portupgrade tho
16 matches
Mail list logo
