Re: [HEADSUP] current switched by default to pkgng
Hello, Baptiste. You wrote 3 ноября 2012 г., 3:56:22: BD> The BSDmc project (http://code.google.com/p/bsdmc/) uses nanobsd BD> and pkgng, have a look in particular at the BD> following diff: http://code.google.com/p/bsdmc/source/detail?r=75 BD> Maybe you can find something helpful for you in there :) Unfortunately, it diverged with nanobsd long time ago and have completely custom package installation function, very complex and unobvious. Now I have only one problem with replacing `pkg_add' with `pkg add' (I've implemented bootstrap of chrooted environment): `pkg add' doesn't have `-F' flag, and attempt to add package twice (first time as dependency and second time because simple nanobsd script doesn't sort packages and add all of them, so required package could be again added after dependant package) leads to non-success return code :( Also, I could not find any documentation about system `pkg' command: `man pkg' shows nothing, `pkg -h' doesn't work, etc. So it is unobvious, where could I read about ASSUME_ALWAYS_YES, PACKAGESITE and other variables, needed for automatic (non-interactive, non-networked) bootstrap. Way to construct proper URL for pkg.txz (with ABI, etc) from script is not clear, too, and automatic downloading doesn't work in chrooted environment, as it doesn't have configured resolver. -- // Black Lion AKA Lev Serebryakov ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On Sat, Nov 03, 2012 at 12:41:31AM +0400, Lev Serebryakov wrote: > Hello, Lev. > You wrote 2 ноября 2012 г., 23:24:28: > > BD>> Make sure to read UPDATING (from ports) to correctly migrate your system > or find > BD>> instruction to make your system still running with legacy pkg_install > tools. > LS> Did somebody update nanobsd scripts? ;-) > Simple replacing "pkg_add" with "pkg add" doesn't work ;-) > > -- > // Black Lion AKA Lev Serebryakov > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" The BSDmc project (http://code.google.com/p/bsdmc/) uses nanobsd and pkgng, have a look in particular at the following diff: http://code.google.com/p/bsdmc/source/detail?r=75 Maybe you can find something helpful for you in there :) regards, Bapt pgpE7pcNRGXXx.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
On Sat, Nov 03, 2012 at 12:41:31AM +0400, Lev Serebryakov wrote: > Hello, Lev. > You wrote 2 ноября 2012 г., 23:24:28: > > BD>> Make sure to read UPDATING (from ports) to correctly migrate your system > or find > BD>> instruction to make your system still running with legacy pkg_install > tools. > LS> Did somebody update nanobsd scripts? ;-) > Simple replacing "pkg_add" with "pkg add" doesn't work ;-) > I know some people have some patches for nanobsd that should work with pkgng, but I don't know much about it. regards, Bapt pgpfb3i653wn8.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
Hello, Lev. You wrote 2 ноября 2012 г., 23:24:28: BD>> Make sure to read UPDATING (from ports) to correctly migrate your system or find BD>> instruction to make your system still running with legacy pkg_install tools. LS> Did somebody update nanobsd scripts? ;-) Simple replacing "pkg_add" with "pkg add" doesn't work ;-) -- // Black Lion AKA Lev Serebryakov ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
Hello, Baptiste. You wrote 10 октября 2012 г., 17:44:21: BD> Make sure to read UPDATING (from ports) to correctly migrate your system or find BD> instruction to make your system still running with legacy pkg_install tools. Did somebody update nanobsd scripts? ;-) -- // Black Lion AKA Lev Serebryakov ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On Sun, Oct 21, 2012 at 5:09 PM, Alex Keda wrote: > On 21.10.2012 13:39, Edho Arief wrote: >> On Sun, Oct 21, 2012 at 4:33 PM, Alex Keda wrote: >>> >>> It update some packages, and install ~20 new packages, named x* >>> >>> How I can say "It's server, I do not need X on them"? >>> >> >> Install the -nox11 variant of the package. > > for example, /usr/ports/editors/vim/Makefile have >> . if defined(NO_GUI) || defined(WITHOUT_GUI) >> WITHOUT_X11=yes >> . endif > > but, it not have -nox11 port > > Athlon5000# pkg search vim > vim-7.3.669Vi "workalike", with many additional > xpi-vimperator-3.5 Vim look and feel for Firefox > ja-jvim-3.0.j2.1a_4Japanized Vim-3.0 > vim-lite-7.3.669 Vi "workalike", with many additional > vimpager-1.7.5 Use ViM as a pager > Athlon5000# Yeah, not all packages have -nox11 port due to current infrastructure and design as previously mentioned. You may want to check vim-lite if it fits your need. At least it does for me. Though honestly, unlike building from ports, upgrading from pkgng is much cheaper (and greener) apart of bandwidth requirement, so I don't find installing few additional packages to be a problem. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 21.10.2012 13:39, Edho Arief wrote: > On Sun, Oct 21, 2012 at 4:33 PM, Alex Keda wrote: >> >> It update some packages, and install ~20 new packages, named x* >> >> How I can say "It's server, I do not need X on them"? >> > > Install the -nox11 variant of the package. for example, /usr/ports/editors/vim/Makefile have > . if defined(NO_GUI) || defined(WITHOUT_GUI) > WITHOUT_X11=yes > . endif but, it not have -nox11 port Athlon5000# pkg search vim vim-7.3.669Vi "workalike", with many additional xpi-vimperator-3.5 Vim look and feel for Firefox ja-jvim-3.0.j2.1a_4Japanized Vim-3.0 vim-lite-7.3.669 Vi "workalike", with many additional vimpager-1.7.5 Use ViM as a pager Athlon5000# ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 21/10/2012 10:33, Alex Keda wrote: > I try use it on my home server. > In make conf, I have >> > WITHOUT_X11=yes >> > NO_GUI=yes > I run pkg2ng, set mirror in pkg.conf > and, run > pkg upgrade -y > > It update some packages, and install ~20 new packages, named x* > > How I can say "It's server, I do not need X on them"? At the moment, that isn't possible using pkgs from the default pkgrepo. Those packages are compiled using the default options settings in the ports, which generally means X support is enabled. So, you need to point your systems at a repo where the pkgs are compiled with your preferred set of options. Which boils down to "set up your own repo." poudriere is a good way of doing that, but possibly overkill if you only have one system to manage. portmaster with the pkgng patches does the job for me. Eventually we hope to make pkgng much more flexible with respect to these sort of configuration choices, but that involves a number of fairly significant changes to the ports (stagedir, sub-packages) as well as some major new functionality in pkgng itself (importing a full solver). Even so, I suspect that for the ultimate in control, compiling from ports will still beat just about anything else. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On Sun, Oct 21, 2012 at 4:33 PM, Alex Keda wrote: > > It update some packages, and install ~20 new packages, named x* > > How I can say "It's server, I do not need X on them"? > Install the -nox11 variant of the package. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
> On 10.10.2012 17:44, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. I try use it on my home server. In make conf, I have > WITHOUT_X11=yes > NO_GUI=yes I run pkg2ng, set mirror in pkg.conf and, run pkg upgrade -y It update some packages, and install ~20 new packages, named x* How I can say "It's server, I do not need X on them"? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 20.10.2012 11:23, Sergey V. Dyatko wrote:
> On Fri, 19 Oct 2012 20:32:31 +0400
> Alex Keda wrote:
>
>> On 19.10.2012 20:21, Alex Keda wrote:
>>> On 19.10.2012 19:59, Chris Rees wrote:
On 19 October 2012 16:16, Alex Keda wrote:
> On 19.10.2012 19:10, Vincent Hoffman wrote:
>> On 19/10/2012 15:39, Alex Keda wrote:
>>> pkg command does not have key for list options - no
>>> autocompletions
>>>
>>> for example, for service command, I use
>>> complete service'n/*/`service -l`/'
>>> in .cshrc
>>>
>>> what I can use for pkg command?
>>
>> horrible but working example
>> pkg help 2>&1 | sed -e '1,/Commands supported:/d ; /For more
>> information on the different commands/,$d; s/^ *// ;
>> s/ .*.*$// ;/^$/d'
>>
>> There's bound to be better ways, I was just bored enough to
>> knock this up. note s/^*// is a tab, while s/ .*.*$// is
>> 2 spaces dont think our sed has any other way to express tab
>> other than an actual tab (ctrl-v then tab on the command line)
>
> it's crazy =)
> may be add -l options?
For Bourne-style shell:
`pkg help 2>&1 | sed -nE 's,^ +(.*),\1,p'`
For csh-style shell:
`pkg help | & sed -nE 's,^ +(.*),\1,p'`
where the bit between ^ and + is a tab character. You can type the
tab character on a command prompt by using Ctrl+V then tab, or just
type it normally in the script.
Hope that helps in the meantime.
Chris
>>> dc7700p# pkg
>>> -cDisplays Performs a and
>>> check debug from insidelocal
>>> package packages remotesearchsystem
>>> updating
>>> -dDisplays Performs a and
>>> . skipped
>>> Displays Opens a against catalogues
>>> debug from insidelink package
>>> packages register searchsystemupdate
>>> dc7700p#
>>> dc7700p# grep pkg /root/.cshrc
>>> complete pkg'n/*/`pkg help |& sed -nE "s,^
>>> +(.*),\1,p"`/'
>>>
>>> some not work... I try my own string:
>>> complete pkg 'n/*/`pkg help |& grep "Commands supported:"
>>> --after-context=100 | grep "^\s" | awk "{print $1}"`/'
>>>
>>> output identical. maybe pipe not work in this place?
>>> ___
>>> freebsd-current@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to
>>> "freebsd-current-unsubscr...@freebsd.org"
>>>
>>
>> it's a good crutch =)
>>
>> dc7700p# pkg
>> addautoremove check create fetch info
>> query remove rquery setshlib update upgrade
>> which
>> audit backup clean delete help install
>> register repo search shell stats updating
>> version
>> dc7700p# pkg
>> dc7700p# grep pkg /root/.cshrc
>> complete pkg 'n/*/`pkg help |& grep "Commands supported:"
>> --after-context=100 | grep "^\s" | cut -d " " -f 1`/'
>> dc7700p#
>>
>>
>
> https://github.com/yoursbofh/pkgng-tcsh/blob/master/dot.cshrc_pkg
>
> Unfortunately, I do not know how to do something like `pkg command
> <-keys> `
>
> i.e.
> 'n/audit/' 'c/-/(F q)/' '`pkg query "%n-%v"`/'
> doesn't work :(
>
> [tiger@laptop]:~%pkg audit [tab]
> Missing separator '/' after completion "".
>
>
>
need escape '
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On Fri, 19 Oct 2012 20:32:31 +0400
Alex Keda wrote:
> On 19.10.2012 20:21, Alex Keda wrote:
> > On 19.10.2012 19:59, Chris Rees wrote:
> >> On 19 October 2012 16:16, Alex Keda wrote:
> >>> On 19.10.2012 19:10, Vincent Hoffman wrote:
> On 19/10/2012 15:39, Alex Keda wrote:
> > pkg command does not have key for list options - no
> > autocompletions
> >
> > for example, for service command, I use
> > complete service'n/*/`service -l`/'
> > in .cshrc
> >
> > what I can use for pkg command?
>
> horrible but working example
> pkg help 2>&1 | sed -e '1,/Commands supported:/d ; /For more
> information on the different commands/,$d; s/^ *// ;
> s/ .*.*$// ;/^$/d'
>
> There's bound to be better ways, I was just bored enough to
> knock this up. note s/^*// is a tab, while s/ .*.*$// is
> 2 spaces dont think our sed has any other way to express tab
> other than an actual tab (ctrl-v then tab on the command line)
> >>>
> >>> it's crazy =)
> >>> may be add -l options?
> >>
> >> For Bourne-style shell:
> >> `pkg help 2>&1 | sed -nE 's,^ +(.*),\1,p'`
> >>
> >> For csh-style shell:
> >> `pkg help | & sed -nE 's,^ +(.*),\1,p'`
> >>
> >> where the bit between ^ and + is a tab character. You can type the
> >> tab character on a command prompt by using Ctrl+V then tab, or just
> >> type it normally in the script.
> >>
> >> Hope that helps in the meantime.
> >>
> >> Chris
> >>
> > dc7700p# pkg
> > -cDisplays Performs a and
> > check debug from insidelocal
> > package packages remotesearchsystem
> > updating
> > -dDisplays Performs a and
> > . skipped
> > Displays Opens a against catalogues
> > debug from insidelink package
> > packages register searchsystemupdate
> > dc7700p#
> > dc7700p# grep pkg /root/.cshrc
> > complete pkg'n/*/`pkg help |& sed -nE "s,^
> > +(.*),\1,p"`/'
> >
> > some not work... I try my own string:
> > complete pkg 'n/*/`pkg help |& grep "Commands supported:"
> > --after-context=100 | grep "^\s" | awk "{print $1}"`/'
> >
> > output identical. maybe pipe not work in this place?
> > ___
> > freebsd-current@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to
> > "freebsd-current-unsubscr...@freebsd.org"
> >
>
> it's a good crutch =)
>
> dc7700p# pkg
> addautoremove check create fetch info
> query remove rquery setshlib update upgrade
> which
> audit backup clean delete help install
> register repo search shell stats updating
> version
> dc7700p# pkg
> dc7700p# grep pkg /root/.cshrc
> complete pkg 'n/*/`pkg help |& grep "Commands supported:"
> --after-context=100 | grep "^\s" | cut -d " " -f 1`/'
> dc7700p#
>
>
https://github.com/yoursbofh/pkgng-tcsh/blob/master/dot.cshrc_pkg
Unfortunately, I do not know how to do something like `pkg command
<-keys> `
i.e.
'n/audit/' 'c/-/(F q)/' '`pkg query "%n-%v"`/'
doesn't work :(
[tiger@laptop]:~%pkg audit [tab]
Missing separator '/' after completion "".
--
wbr, tiger
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 19.10.2012 20:21, Alex Keda wrote:
> On 19.10.2012 19:59, Chris Rees wrote:
>> On 19 October 2012 16:16, Alex Keda wrote:
>>> On 19.10.2012 19:10, Vincent Hoffman wrote:
On 19/10/2012 15:39, Alex Keda wrote:
> pkg command does not have key for list options - no autocompletions
>
> for example, for service command, I use
> complete service'n/*/`service -l`/'
> in .cshrc
>
> what I can use for pkg command?
horrible but working example
pkg help 2>&1 | sed -e '1,/Commands supported:/d ; /For more information
on the different commands/,$d; s/^ *// ; s/ .*.*$// ;/^$/d'
There's bound to be better ways, I was just bored enough to knock this up.
note s/^*// is a tab, while s/ .*.*$// is 2 spaces
dont think our sed has any other way to express tab other than an actual
tab (ctrl-v then tab on the command line)
>>>
>>> it's crazy =)
>>> may be add -l options?
>>
>> For Bourne-style shell:
>> `pkg help 2>&1 | sed -nE 's,^ +(.*),\1,p'`
>>
>> For csh-style shell:
>> `pkg help | & sed -nE 's,^ +(.*),\1,p'`
>>
>> where the bit between ^ and + is a tab character. You can type the
>> tab character on a command prompt by using Ctrl+V then tab, or just
>> type it normally in the script.
>>
>> Hope that helps in the meantime.
>>
>> Chris
>>
> dc7700p# pkg
> -cDisplays Performs a and
> check debug from insidelocal
> package packages remotesearchsystem
> updating
> -dDisplays Performs a and
> . skipped
> Displays Opens a against catalogues
> debug from insidelink package
> packages register searchsystemupdate
> dc7700p#
> dc7700p# grep pkg /root/.cshrc
> complete pkg'n/*/`pkg help |& sed -nE "s,^ +(.*),\1,p"`/'
>
> some not work... I try my own string:
> complete pkg 'n/*/`pkg help |& grep "Commands supported:"
> --after-context=100 | grep "^\s" | awk "{print $1}"`/'
>
> output identical. maybe pipe not work in this place?
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
it's a good crutch =)
dc7700p# pkg
addautoremove check create fetch info query
remove rquery setshlib update upgrade
which
audit backup clean delete help install
register repo search shell stats updating
version
dc7700p# pkg
dc7700p# grep pkg /root/.cshrc
complete pkg 'n/*/`pkg help |& grep "Commands supported:"
--after-context=100 | grep "^\s" | cut -d " " -f 1`/'
dc7700p#
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 19.10.2012 19:59, Chris Rees wrote:
> On 19 October 2012 16:16, Alex Keda wrote:
>> On 19.10.2012 19:10, Vincent Hoffman wrote:
>>> On 19/10/2012 15:39, Alex Keda wrote:
pkg command does not have key for list options - no autocompletions
for example, for service command, I use
complete service'n/*/`service -l`/'
in .cshrc
what I can use for pkg command?
>>>
>>> horrible but working example
>>> pkg help 2>&1 | sed -e '1,/Commands supported:/d ; /For more information
>>> on the different commands/,$d; s/^ *// ; s/ .*.*$// ;/^$/d'
>>>
>>> There's bound to be better ways, I was just bored enough to knock this up.
>>> note s/^*// is a tab, while s/ .*.*$// is 2 spaces
>>> dont think our sed has any other way to express tab other than an actual
>>> tab (ctrl-v then tab on the command line)
>>
>> it's crazy =)
>> may be add -l options?
>
> For Bourne-style shell:
> `pkg help 2>&1 | sed -nE 's,^ +(.*),\1,p'`
>
> For csh-style shell:
> `pkg help | & sed -nE 's,^ +(.*),\1,p'`
>
> where the bit between ^ and + is a tab character. You can type the
> tab character on a command prompt by using Ctrl+V then tab, or just
> type it normally in the script.
>
> Hope that helps in the meantime.
>
> Chris
>
dc7700p# pkg
-cDisplays Performs a and
check debug from insidelocal
package packages remotesearchsystem
updating
-dDisplays Performs a and
. skipped
Displays Opens a against catalogues
debug from insidelink package
packages register searchsystemupdate
dc7700p#
dc7700p# grep pkg /root/.cshrc
complete pkg'n/*/`pkg help |& sed -nE "s,^ +(.*),\1,p"`/'
some not work... I try my own string:
complete pkg 'n/*/`pkg help |& grep "Commands supported:"
--after-context=100 | grep "^\s" | awk "{print $1}"`/'
output identical. maybe pipe not work in this place?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 19 October 2012 16:16, Alex Keda wrote: > On 19.10.2012 19:10, Vincent Hoffman wrote: >> On 19/10/2012 15:39, Alex Keda wrote: >>> On 10.10.2012 17:44, Baptiste Daroussin wrote: Hi all, If you are using the ports tree on a FreeBSD current setup, then you are concerned by the announce. As nvidia-drivers has been fixed and is now properly working with pkgng, the ports tree as been switch by default to use pkgng on FreeBSD Current based on version >= 117 which was the version when we tested the switch code. Make sure to read UPDATING (from ports) to correctly migrate your system or find instruction to make your system still running with legacy pkg_install tools. regards, Bapt >>> pkg command does not have key for list options - no autocompletions >>> >>> for example, for service command, I use >>> complete service'n/*/`service -l`/' >>> in .cshrc >>> >>> what I can use for pkg command? >> >> horrible but working example >> pkg help 2>&1 | sed -e '1,/Commands supported:/d ; /For more information >> on the different commands/,$d; s/^ *// ; s/ .*.*$// ;/^$/d' >> >> There's bound to be better ways, I was just bored enough to knock this up. >> note s/^*// is a tab, while s/ .*.*$// is 2 spaces >> dont think our sed has any other way to express tab other than an actual >> tab (ctrl-v then tab on the command line) > > it's crazy =) > may be add -l options? For Bourne-style shell: `pkg help 2>&1 | sed -nE 's,^ +(.*),\1,p'` For csh-style shell: `pkg help | & sed -nE 's,^ +(.*),\1,p'` where the bit between ^ and + is a tab character. You can type the tab character on a command prompt by using Ctrl+V then tab, or just type it normally in the script. Hope that helps in the meantime. Chris ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 19.10.2012 19:10, Vincent Hoffman wrote: > On 19/10/2012 15:39, Alex Keda wrote: >> On 10.10.2012 17:44, Baptiste Daroussin wrote: >>> Hi all, >>> >>> If you are using the ports tree on a FreeBSD current setup, then you are >>> concerned by the announce. >>> >>> As nvidia-drivers has been fixed and is now properly working with pkgng, the >>> ports tree as been switch by default to use pkgng on FreeBSD Current based >>> on >>> version >= 117 which was the version when we tested the switch code. >>> >>> Make sure to read UPDATING (from ports) to correctly migrate your system or >>> find >>> instruction to make your system still running with legacy pkg_install tools. >>> >>> regards, >>> Bapt >>> >> pkg command does not have key for list options - no autocompletions >> >> for example, for service command, I use >> complete service'n/*/`service -l`/' >> in .cshrc >> >> what I can use for pkg command? > > horrible but working example > pkg help 2>&1 | sed -e '1,/Commands supported:/d ; /For more information > on the different commands/,$d; s/^ *// ; s/ .*.*$// ;/^$/d' > > There's bound to be better ways, I was just bored enough to knock this up. > note s/^*// is a tab, while s/ .*.*$// is 2 spaces > dont think our sed has any other way to express tab other than an actual > tab (ctrl-v then tab on the command line) it's crazy =) may be add -l options? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 19/10/2012 15:39, Alex Keda wrote: > On 10.10.2012 17:44, Baptiste Daroussin wrote: >> Hi all, >> >> If you are using the ports tree on a FreeBSD current setup, then you are >> concerned by the announce. >> >> As nvidia-drivers has been fixed and is now properly working with pkgng, the >> ports tree as been switch by default to use pkgng on FreeBSD Current based on >> version >= 117 which was the version when we tested the switch code. >> >> Make sure to read UPDATING (from ports) to correctly migrate your system or >> find >> instruction to make your system still running with legacy pkg_install tools. >> >> regards, >> Bapt >> > pkg command does not have key for list options - no autocompletions > > for example, for service command, I use > complete service'n/*/`service -l`/' > in .cshrc > > what I can use for pkg command? horrible but working example pkg help 2>&1 | sed -e '1,/Commands supported:/d ; /For more information on the different commands/,$d; s/^ *// ; s/ .*.*$// ;/^$/d' There's bound to be better ways, I was just bored enough to knock this up. note s/^*// is a tab, while s/ .*.*$// is 2 spaces dont think our sed has any other way to express tab other than an actual tab (ctrl-v then tab on the command line) Vince > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 8:44 AM, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. > > regards, > Bapt > In case anyone missed it. Both ports-mgmt/portmaster and ports-mgmt/portupgrade will work with PKGNG now. For portmaster, you will need to select the PKGNGPATCH currently. The plan is to not require the patch for the next portmaster version, to support both pkg_install and pkgng out-of-box. -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 10.10.2012 17:44, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. > > regards, > Bapt > pkg command does not have key for list options - no autocompletions for example, for service command, I use complete service'n/*/`service -l`/' in .cshrc what I can use for pkg command? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
Am 11.10.2012 08:02, schrieb Matthew Seaman:
> On 10/10/2012 23:20, Vincent Hoffman wrote:
>>> That's if you were to patch an already installed copy of
>>> portmaster.
The patch is designed to be placed in
${PORTSDIR}/ports-mgmt/portmaster/files/
so it would be applied as part of the normal process of
building the portmaster port. In which case portmaster.sh.in
is definitely the correct target.
>
>> Actually not so, maybe something has changed recently?
Definitely ;-)
> I stand corrected. Looks like Bryan switched things around a bit
> when he imported everything to GitHub.
>
> I'll fix the patch pro-tem although it should become redundant Real
> Soon Now.
My first assumption was, that the patch had already been integrated
into portmaster, when it failed to apply to the updated port. But the
resulting portmaster script did not support PKGNG, which made me look
for an updated patch and finally try to apply the previous patch to
the renamed file fetched by the port.
I just wanted to point out, that while the patch from October 2nd
does no longer find the file to patch (since it has been renamed),
that it still is required (with the changed filename). It took me
some time to resolve this issue and I just wanted to spare others
from wasting their time ...
Regards, STefan
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 23:20, Vincent Hoffman wrote:
>> That's if you were to patch an already installed copy of portmaster.
>> > The patch is designed to be placed in
>> >
>> > ${PORTSDIR}/ports-mgmt/portmaster/files/
>> >
>> > so it would be applied as part of the normal process of building the
>> > portmaster port. In which case portmaster.sh.in is definitely the
>> > correct target.
> Actually not so, maybe something has changed recently?
I stand corrected. Looks like Bryan switched things around a bit when
he imported everything to GitHub.
I'll fix the patch pro-tem although it should become redundant Real Soon
Now.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 20:50, Matthew Seaman wrote:
> On 10/10/2012 19:35, Stefan Esser wrote:
>> Am 10.10.2012 19:14, schrieb Matthew Seaman:
>>> On 10/10/2012 15:07, O. Hartmann wrote:
Is ports-mgmt/portmaster now dealing with pkgng?
>>>
>>> Not yet. bdrewery has taken over the portmaster port and pkgng
>>> related updates are expected in the near future.
>>>
>>> Until then, you still need to follow the instructions here:
>>>
>>> https://github.com/pkgng/pkgng/blob/master/FAQ.md#15
>>
>> In order to get the portmaster-pkgng patch to apply,
>> the filename in the second line must be changed:
>>
>> from ./portmaster.sh.in
>> to ./portmaster
>
> That's if you were to patch an already installed copy of portmaster.
> The patch is designed to be placed in
>
> ${PORTSDIR}/ports-mgmt/portmaster/files/
>
> so it would be applied as part of the normal process of building the
> portmaster port. In which case portmaster.sh.in is definitely the
> correct target.
Actually not so, maybe something has changed recently?
[root@ostracod /usr/ports/ports-mgmt/portmaster]# head -4
files/patch-portmaster-pkgng
--- ./portmaster.sh.in.orig 2012-10-01 09:34:15.0 +0100
+++ ./portmaster.sh.in 2012-10-02 18:14:34.319249588 +0100
@@ -47,7 +47,7 @@
#=== Begin functions we always want to have ===
[root@ostracod /usr/ports/ports-mgmt/portmaster]# make patch
===> License BSD accepted by the user
===> Found saved configuration for portmaster-3.11
===> portmaster-3.14 depends on file: /usr/local/sbin/pkg - found
===> Extracting for portmaster-3.14
=> SHA256 Checksum OK for portmaster-portmaster-3.14-31009f6.tar.gz.
===> Patching for portmaster-3.14
===> Applying FreeBSD patches for portmaster-3.14
File to patch: ^C=> Patch patch-portmaster-pkgng failed to apply cleanly.
While if edited as suggested
[root@ostracod /usr/ports/ports-mgmt/portmaster]# !head
head -4 files/patch-portmaster-pkgng
--- ./portmaster.sh.in.orig 2012-10-01 09:34:15.0 +0100
+++ ./portmaster2012-10-02 18:14:34.319249588 +0100
@@ -47,7 +47,7 @@
#=== Begin functions we always want to have ===
[root@ostracod /usr/ports/ports-mgmt/portmaster]# make patch
===> License BSD accepted by the user
===> Found saved configuration for portmaster-3.11
===> portmaster-3.14 depends on file: /usr/local/sbin/pkg - found
===> Extracting for portmaster-3.14
=> SHA256 Checksum OK for portmaster-portmaster-3.14-31009f6.tar.gz.
===> Patching for portmaster-3.14
===> Applying FreeBSD patches for portmaster-3.14
[root@ostracod /usr/ports/ports-mgmt/portmaster]#
Vince
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 19:35, Stefan Esser wrote:
> Am 10.10.2012 19:14, schrieb Matthew Seaman:
>> On 10/10/2012 15:07, O. Hartmann wrote:
>>> Is ports-mgmt/portmaster now dealing with pkgng?
>>
>> Not yet. bdrewery has taken over the portmaster port and pkgng
>> related updates are expected in the near future.
>>
>> Until then, you still need to follow the instructions here:
>>
>> https://github.com/pkgng/pkgng/blob/master/FAQ.md#15
>
> In order to get the portmaster-pkgng patch to apply,
> the filename in the second line must be changed:
>
> from ./portmaster.sh.in
> to./portmaster
That's if you were to patch an already installed copy of portmaster.
The patch is designed to be placed in
${PORTSDIR}/ports-mgmt/portmaster/files/
so it would be applied as part of the normal process of building the
portmaster port. In which case portmaster.sh.in is definitely the
correct target.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey
signature.asc
Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
Am 10.10.2012 19:14, schrieb Matthew Seaman: > On 10/10/2012 15:07, O. Hartmann wrote: >> Is ports-mgmt/portmaster now dealing with pkgng? > > Not yet. bdrewery has taken over the portmaster port and pkgng > related updates are expected in the near future. > > Until then, you still need to follow the instructions here: > > https://github.com/pkgng/pkgng/blob/master/FAQ.md#15 In order to get the portmaster-pkgng patch to apply, the filename in the second line must be changed: from./portmaster.sh.in to ./portmaster Regards, STefan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 07:11:22PM +0200, Victor Balada Diaz wrote: > On Wed, Oct 10, 2012 at 06:31:49PM +0200, Baptiste Daroussin wrote: > > Yes there is http://pkg.FreeBSD.org (no website in there no need to try to > > there) which will point you to pkgbeta.freebsd.org where some packages > > resides. > > > > Unfortunatly the package building cluster needs some time to get more > > reliable > > and thus the packages out there are not updated very often. > > > > regards, > > Bapt > > Is there anything we can do to help with build cluster reliability? > > Regards. > Victor. > -- > La prueba más fehaciente de que existe vida inteligente en otros > planetas, es que no han intentado contactar con nosotros. 1/ send me motivation :) 2/ if you are willing to code the new version, please contact me in private I'll share the designs, code repository and how it works. beware the architecture needed to test is not trivial at all :D regards, Bapt pgpwg342kKvKE.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 10:14 AM, Matthew Seaman wrote: > On 10/10/2012 15:07, O. Hartmann wrote: >> Is ports-mgmt/portmaster now dealing with pkgng? > > Not yet. bdrewery has taken over the portmaster port and pkgng related > updates are expected in the near future. > > Until then, you still need to follow the instructions here: > > https://github.com/pkgng/pkgng/blob/master/FAQ.md#15 Ok, nevermind. That's what I get for running make patch but not actually following through figuring out why the make patch didn't stick :). -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 7:07 AM, O. Hartmann wrote: > On 10/10/12 15:44, Baptiste Daroussin wrote: >> Hi all, >> >> If you are using the ports tree on a FreeBSD current setup, then you are >> concerned by the announce. >> >> As nvidia-drivers has been fixed and is now properly working with pkgng, the >> ports tree as been switch by default to use pkgng on FreeBSD Current based on >> version >= 117 which was the version when we tested the switch code. >> >> Make sure to read UPDATING (from ports) to correctly migrate your system or >> find >> instruction to make your system still running with legacy pkg_install tools. >> >> regards, >> Bapt >> > > Thank you very much. > > Is ports-mgmt/portmaster now dealing with pkgng? Hmm.. looks like it is now. Thanks, -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 15:07, O. Hartmann wrote: > Is ports-mgmt/portmaster now dealing with pkgng? Not yet. bdrewery has taken over the portmaster port and pkgng related updates are expected in the near future. Until then, you still need to follow the instructions here: https://github.com/pkgng/pkgng/blob/master/FAQ.md#15 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 06:31:49PM +0200, Baptiste Daroussin wrote: > Yes there is http://pkg.FreeBSD.org (no website in there no need to try to > there) which will point you to pkgbeta.freebsd.org where some packages > resides. > > Unfortunatly the package building cluster needs some time to get more reliable > and thus the packages out there are not updated very often. > > regards, > Bapt Is there anything we can do to help with build cluster reliability? Regards. Victor. -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 2:44 PM, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. I read UPDATING, but I'm still not sure what this means when I use ports and not packages. Does it mean that I should install pkg to have /var/db/pkg managed, but otherwise ports keeps working the same way, or? -- Simon L. B. Nielsen ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
--- On Wed, 10/10/12, Glen Barber wrote: > From: Glen Barber > Subject: Re: [HEADSUP] current switched by default to pkgng > To: "Baptiste Daroussin" > Cc: po...@freebsd.org, ports-annou...@freebsd.org, curr...@freebsd.org > Date: Wednesday, October 10, 2012, 6:51 AM > On Wed, Oct 10, 2012 at 03:44:21PM > +0200, Baptiste Daroussin wrote: > > Hi all, > > > > If you are using the ports tree on a FreeBSD current > setup, then you are > > concerned by the announce. > > > > As nvidia-drivers has been fixed and is now properly > working with pkgng, the > > ports tree as been switch by default to use pkgng on > FreeBSD Current based on > > version >= 117 which was the version when we > tested the switch code. > > > > Make sure to read UPDATING (from ports) to correctly > migrate your system or find > > instruction to make your system still running with > legacy pkg_install tools. > > > > Congratulations, and thank you for all of your hard work on > this! > > Glen > > I was/am confused by the UPDATING instructions. To make the switch: (which switch, and only for V10, from which to which?) ... Before and after step 3, how specifically is the system set up? ... Should any of this be done by persons using V9 immediately before a v9 v10 upgrade? And can another synopsis be written for those before the upgrade, specifically to prepare for either case after the upgrade? IOW more subsections and a longer explanation. (I think maybe more context before/after some of the steps in the procedure...) Just a suggestion. I could probably figure it all out later... J. Bouquet ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 10/10/12 15:44, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. > > regards, > Bapt > Thank you very much. Is ports-mgmt/portmaster now dealing with pkgng? Regards, Oliver ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 17:43, Bruce Cran wrote: > On 10/10/2012 17:31, Baptiste Daroussin wrote: >> Yes there is http://pkg.FreeBSD.org (no website in there no need to >> try to there) which will point you to pkgbeta.freebsd.org where some >> packages resides. > > On my systems pkg.freebsd.org doesn't seem to exist: > >> ping pkg.freebsd.org > ping: cannot resolve pkg.freebsd.org: No address associated with name > % dig IN SRV _http._tcp.pkg.freebsd.org ; <<>> DiG 9.8.3-P1 <<>> IN SRV _http._tcp.pkg.freebsd.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34727 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;_http._tcp.pkg.freebsd.org.IN SRV ;; ANSWER SECTION: _http._tcp.pkg.freebsd.org. 3600 IN SRV 10 10 80 pkgbeta.FreeBSD.org. ;; Query time: 71 msec ;; SERVER: ::1#53(::1) ;; WHEN: Wed Oct 10 17:50:20 2012 ;; MSG SIZE rcvd: 83 -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 17:31, Baptiste Daroussin wrote: Yes there is http://pkg.FreeBSD.org (no website in there no need to try to there) which will point you to pkgbeta.freebsd.org where some packages resides. On my systems pkg.freebsd.org doesn't seem to exist: > ping pkg.freebsd.org ping: cannot resolve pkg.freebsd.org: No address associated with name -- Bruce Cran ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 16:52, Simon L. B. Nielsen wrote: > I read UPDATING, but I'm still not sure what this means when I use > ports and not packages. It means that if you're a user of HEAD, and you don't opt out by setting WITHOUT_PKGNG=yes in make.conf, then: * the next time you use the ports, ports-mgmt/pkg will be installed as a dependency * pkgng will be used to register all the ports you subsequently install into /var/db/pkg/local.sqlite However, unless you take some preventive action, any ports that were installed before this update won't be added to the registry in local.sqlite. You'll end up with a mix of stuff using the old subdirs of /var/db/pkg from pkg_tools and the new local.sqlite from pkgng. Sorting that out is a one-time job to import the pkg_tools data into pkgng's database using pkg2ng, which is what the instructions in UPDATING describe. > Does it mean that I should install pkg to have /var/db/pkg managed, > but otherwise ports keeps working the same way, or? pkgng will need to be installed, yes. You'll need to switch to using pkgng commands rather than pkg_tools -- eg: pkg info -a to get a list of all installed ports. You need to patch portmaster(8) if you use that -- although a patched version will soon be available in ports. Apart from that, the ports will work pretty much exactly as they used to do. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 06:25:08PM +0200, Victor Balada Diaz wrote: > On Wed, Oct 10, 2012 at 03:44:21PM +0200, Baptiste Daroussin wrote: > > Hi all, > > > > If you are using the ports tree on a FreeBSD current setup, then you are > > concerned by the announce. > > > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > > ports tree as been switch by default to use pkgng on FreeBSD Current based > > on > > version >= 117 which was the version when we tested the switch code. > > > > Make sure to read UPDATING (from ports) to correctly migrate your system or > > find > > instruction to make your system still running with legacy pkg_install tools. > > > > regards, > > Bapt > > Hello Baptiste, > > Thanks a lot for your hard work. > > I've been using pkgng for a while on 9.0 and it's been a great experience. > > Right now you can use pointyhat packages[1] if you use old pkg tools. Is > there any plan to create binary packages more often than once per release? > > Regards. > Victor. > > [1]: http://pointyhat.freebsd.org/errorlogs/amd64-10-packages-latest/ > -- > La prueba más fehaciente de que existe vida inteligente en otros > planetas, es que no han intentado contactar con nosotros. Yes there is http://pkg.FreeBSD.org (no website in there no need to try to there) which will point you to pkgbeta.freebsd.org where some packages resides. Unfortunatly the package building cluster needs some time to get more reliable and thus the packages out there are not updated very often. regards, Bapt pgpOuMExyOSpU.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 04:52:45PM +0100, Simon L. B. Nielsen wrote: > On Wed, Oct 10, 2012 at 2:44 PM, Baptiste Daroussin wrote: > > Hi all, > > > > If you are using the ports tree on a FreeBSD current setup, then you are > > concerned by the announce. > > > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > > ports tree as been switch by default to use pkgng on FreeBSD Current based > > on > > version >= 117 which was the version when we tested the switch code. > > > > Make sure to read UPDATING (from ports) to correctly migrate your system or > > find > > instruction to make your system still running with legacy pkg_install tools. > > I read UPDATING, but I'm still not sure what this means when I use > ports and not packages. > > Does it mean that I should install pkg to have /var/db/pkg managed, > but otherwise ports keeps working the same way, or? > > -- > Simon L. B. Nielsen That means you either have to add WITHOUT_PKGNG to you make.conf so that nothing changes for you or follow the procedure (which is for ports only) and your local ports will be managed by pkgng, and you can forget about all the pkg_* tools :) regards, Bapt pgpCE4csaTwqK.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 03:44:21PM +0200, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. > > regards, > Bapt Hello Baptiste, Thanks a lot for your hard work. I've been using pkgng for a while on 9.0 and it's been a great experience. Right now you can use pointyhat packages[1] if you use old pkg tools. Is there any plan to create binary packages more often than once per release? Regards. Victor. [1]: http://pointyhat.freebsd.org/errorlogs/amd64-10-packages-latest/ -- La prueba más fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 08:42:39AM -0700, Jeffrey Bouquet wrote: > > > --- On Wed, 10/10/12, Glen Barber wrote: > > > From: Glen Barber > > Subject: Re: [HEADSUP] current switched by default to pkgng > > To: "Baptiste Daroussin" > > Cc: po...@freebsd.org, ports-annou...@freebsd.org, curr...@freebsd.org > > Date: Wednesday, October 10, 2012, 6:51 AM > > On Wed, Oct 10, 2012 at 03:44:21PM > > +0200, Baptiste Daroussin wrote: > > > Hi all, > > > > > > If you are using the ports tree on a FreeBSD current > > setup, then you are > > > concerned by the announce. > > > > > > As nvidia-drivers has been fixed and is now properly > > working with pkgng, the > > > ports tree as been switch by default to use pkgng on > > FreeBSD Current based on > > > version >= 117 which was the version when we > > tested the switch code. > > > > > > Make sure to read UPDATING (from ports) to correctly > > migrate your system or find > > > instruction to make your system still running with > > legacy pkg_install tools. > > > > > > > Congratulations, and thank you for all of your hard work on > > this! > > > > Glen > > > > > I was/am confused by the UPDATING instructions. > To make the switch: (which switch, and only for V10, from which > to which?) > ... > Before and after step 3, how specifically is the system set up? > ... > Should any of this be done by persons using V9 immediately before > a v9 v10 upgrade? And can another synopsis be written for those > before the upgrade, specifically to prepare for either case > after the upgrade? > IOW more subsections and a longer explanation. (I think maybe more > context before/after some of the steps in the procedure...) > > > Just a suggestion. I could probably figure it all out later... the AFFECT line was updated to specify which version of FreeBSD are concerned. This also concern people doing an upgrade from v9 to v10, but after the upgrade to v10. regards, Bapt pgpPqxtHpeEkW.pgp Description: PGP signature
Re: [HEADSUP] current switched by default to pkgng
On 10/10/2012 15:44, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. Thank you! signature.asc Description: OpenPGP digital signature
Re: [HEADSUP] current switched by default to pkgng
On Wed, Oct 10, 2012 at 03:44:21PM +0200, Baptiste Daroussin wrote: > Hi all, > > If you are using the ports tree on a FreeBSD current setup, then you are > concerned by the announce. > > As nvidia-drivers has been fixed and is now properly working with pkgng, the > ports tree as been switch by default to use pkgng on FreeBSD Current based on > version >= 117 which was the version when we tested the switch code. > > Make sure to read UPDATING (from ports) to correctly migrate your system or > find > instruction to make your system still running with legacy pkg_install tools. > Congratulations, and thank you for all of your hard work on this! Glen pgpwaQS43VTNl.pgp Description: PGP signature
[HEADSUP] current switched by default to pkgng
Hi all, If you are using the ports tree on a FreeBSD current setup, then you are concerned by the announce. As nvidia-drivers has been fixed and is now properly working with pkgng, the ports tree as been switch by default to use pkgng on FreeBSD Current based on version >= 117 which was the version when we tested the switch code. Make sure to read UPDATING (from ports) to correctly migrate your system or find instruction to make your system still running with legacy pkg_install tools. regards, Bapt pgpz7S7kRpT25.pgp Description: PGP signature
