Hi,
On Thu, 10 Apr 2014, RW wrote:
It's newer than the recently reworked version of the options
framework, but /var/db/port was used for options before that.
Aha! So that's what I missed, thank you.
It also doesn't affect me, since I now build my packages using
PORT_DBDIR=/var/db/ports/$mach
On Thu, 10 Apr 2014 15:03:09 +0100
RW wrote:
> It's newer than the recently reworked version of the options
> framework, but /var/db/port was used for options before that.
Sorry, I meant: the recently reworked version of the options
framework is newer than portmaster,
___
On Thu, 10 Apr 2014 08:07:55 -0500
Scot Hetzel wrote:
> Portmaster is not breaking hier(7).
It's not, because it's information about what was used to build the
packages, so /var/db/pkg is a legitimate location.
> Portmaster was originally designed to use the old pkg tools
> (pkg_install, ...),
On Thu, Apr 10, 2014 at 5:45 AM, Melvyn Sopacua wrote:
> Hi,
>
>
> On Wed, 9 Apr 2014, John Marino wrote:
>
>>> This still doesn't make sense. Distfiles are of no concern to binary
>>> packages, so why would I continue to clutter /var/db/pkg with a large
>>> tree of directories that is then duplic
Hi,
On Wed, 9 Apr 2014, John Marino wrote:
This still doesn't make sense. Distfiles are of no concern to binary
packages, so why would I continue to clutter /var/db/pkg with a large
tree of directories that is then duplicated to /var/db/ports?
What problem in portmaster or the options framework
On Wed, 9 Apr 2014, Melvyn Sopacua wrote:
Hi,
So, after the detour...
On 4/9/2014 12:38, Melvyn Sopacua wrote:
Though it makes no sense in my mind. Distfiles belong to ports not
packages. What problem was solved by moving this?
This still doesn't make sense. Distfiles are of no concern
On 4/9/2014 20:17, Melvyn Sopacua wrote:
> Hi,
>
> So, after the detour...
There was no detour. You were given a comprehensive answer.
>>> On 4/9/2014 12:38, Melvyn Sopacua wrote:
>
Though it makes no sense in my mind. Distfiles belong to ports not
packages. What problem was solved
Hi,
So, after the detour...
On 4/9/2014 12:38, Melvyn Sopacua wrote:
Though it makes no sense in my mind. Distfiles belong to ports not
packages. What problem was solved by moving this?
This still doesn't make sense. Distfiles are of no concern to binary
packages, so why would I continue
Adam McDougall wrote:
>> A clean /var/db/pkg has these contents (or similar):
>> auditfile
>> local.sqlite
>> repo-FreeBSD.sqlite
>> vuln.xml
>>
>> A clean /var/db/ports directory has these contents
>> */options
>>
>> That's it. No distfiles.
>
> I believe I've heard /var/db/pkg/some
On Wed, Apr 9, 2014 at 3:58 AM, John Marino wrote:
> On 4/9/2014 12:38, Melvyn Sopacua wrote:
> > Hi,
> >
> > On Tue, 8 Apr 2014, Kevin Oberman wrote:
> >
> /var/db/pkg/libyaml-0.1.6/distfiles
> > ...
> >>
> >> No, once you run pkgng, these files are in /var/db/pkg. The only files
> in
> >> /
On 04/09/2014 06:58, John Marino wrote:
> On 4/9/2014 12:38, Melvyn Sopacua wrote:
>> Hi,
>>
>> On Tue, 8 Apr 2014, Kevin Oberman wrote:
>>
> /var/db/pkg/libyaml-0.1.6/distfiles
>> ...
>>>
>>> No, once you run pkgng, these files are in /var/db/pkg. The only files in
>>> /var/db/ports are option
On 4/9/2014 12:38, Melvyn Sopacua wrote:
> Hi,
>
> On Tue, 8 Apr 2014, Kevin Oberman wrote:
>
/var/db/pkg/libyaml-0.1.6/distfiles
> ...
>>
>> No, once you run pkgng, these files are in /var/db/pkg. The only files in
>> /var/db/ports are options files.
>
> Ah, my bad.
> Though it makes no se
Hi,
On Tue, 8 Apr 2014, Kevin Oberman wrote:
/var/db/pkg/libyaml-0.1.6/distfiles
...
No, once you run pkgng, these files are in /var/db/pkg. The only files in
/var/db/ports are options files.
Ah, my bad.
Though it makes no sense in my mind. Distfiles belong to ports not
packages. What prob
On Tue, Apr 8, 2014 at 12:44 PM, Melvyn Sopacua wrote:
> Hi,
>
> On Wed, 2 Apr 2014, Jakob Breivik Grimstveit wrote:
>
>
> /var/db/pkg only contains these files:
>>
>> $ find /var/db/pkg
>> [...]
>> /var/db/pkg/libyaml-0.1.6
>> /var/db/pkg/libyaml-0.1.6/distfiles
>> /var/db/pkg/gcc-ecj-4.5
>> /v
Hi,
On Wed, 2 Apr 2014, Jakob Breivik Grimstveit wrote:
/var/db/pkg only contains these files:
$ find /var/db/pkg
[...]
/var/db/pkg/libyaml-0.1.6
/var/db/pkg/libyaml-0.1.6/distfiles
/var/db/pkg/gcc-ecj-4.5
/var/db/pkg/gcc-ecj-4.5/distfiles
/var/db/pkg/cmake-modules-2.8.10.2
/var/db/pkg/cmake-
On 03/04/2014 00:00, Kevin Oberman wrote:
> Your best bet is to learn the appropriate commands in pkg. Start with "pkg
> help info". For te most part, portmaster is unchanged including portmaster
> -l. Among the changes you might notice is speed. Most operations are much
> faster. E.g. "pkg version
On Wed, Apr 2, 2014 at 5:27 AM, Jakob Breivik Grimstveit <
ja...@grimstveit.no> wrote:
> Hi,
>
> After having done some half-hearted pkgng conversions back in the fbsd 9.x
> days I'm now on fbsd 10.
>
> I use `portmaster -a -v -d --delete-packages` to upgrade packages
>
> Trying to convert to new
Jakob Breivik Grimstveit writes:
> Hi,
>
> After having done some half-hearted pkgng conversions back in the fbsd 9.x
> days I'm now on fbsd 10.
>
> I use `portmaster -a -v -d --delete-packages` to upgrade packages
>
> Trying to convert to new pkg format fails:
>
> # pkg2ng
> Converting packages
Hi,
After having done some half-hearted pkgng conversions back in the fbsd 9.x
days I'm now on fbsd 10.
I use `portmaster -a -v -d --delete-packages` to upgrade packages
Trying to convert to new pkg format fails:
# pkg2ng
Converting packages from /var/db/pkg
[...]
Converting libyaml-0.1.6...
pk
19 matches
Mail list logo
