Date: Thu, 19 Dec 2013 13:51:22 -0500 From: Adam Weinberger <adamw@adamw.org> To: Bryan Drewery <bryan@shatow.net> Cc: pkg@freebsd.org, owner-ports-committers@freebsd.org, ports-committers@freebsd.org Subject: Re: ruBSD 2013 pkg talk report Message-ID: <b8bed5c7cf8c4d3a5ef05fb8d81f1482@apnoea.adamw.org> In-Reply-To: <52B344C1.80304@shatow.net> References: <52B0E8B8.4030506@FreeBSD.org> <52B344C1.80304@shatow.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013/12/19 14:10, Bryan Drewery wrote:
> On 12/17/2013 6:13 PM, Vsevolod Stakhov wrote:
>> Q: What about portupgrade and other related tools? A: I claimed
>> that these tools are going to be deprecated and packages will be
>> managed from pkg even if you want to build a custom package from
>> the sources.
>
> These tools are not deprecated for port building. portupgrade and
> portmaster will live on. They are port building tools. pkg is not.
> These are only no longer intended to be used to install packages.
This was one of my very first questions about pkgng, and in fact I was
not 100% clear on this until your email here. That information would be
really helpful to have on the wiki, and even in UPDATING. Too many
entries (especially from the initial roll-out) say "all users should..."
when it really means "all package-based users." The words "packages" and
"ports" is just not clearly defined in the wiki pages, and I think it'd
help to clarify them.
It would be good to highlight that:
* Building, installing and upgrading ports ("using make(1)") is exactly
the same
* pkgng DOES change how information about installed ports is stored
* portmaster/portupgrade should no longer be used to manage packages
("binary distributions created from ports")
# Adam
---
Adam Weinberger
adamw@adamw.org
http://www.adamw.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b8bed5c7cf8c4d3a5ef05fb8d81f1482>