Re: How does pkg_add know I'm tracking -stable?
On 2014-09-23, Henning Brauer hb-open...@ml.bsws.de wrote: pkg_add doesn't know or care about release/stable/current/frankenstein. The packages itself are built against a certain set of libraries and thus care (and pkg_add checks that). libraries don't change versions in -stable, pretty much by definition. to a smaller extent the same applies to syscalls and some other interfaces, but we get into nitpicking. you tell pkg_add a source for your packages, that's it. The only addition I have to this is that fixes are committed to -stable ports, so there are updates for these available, but official packages aren't built for these. They are available from a third party though, see https://stable.mtier.org/.
How does pkg_add know I'm tracking -stable?
I've built both /usr/src and /usr/xenocara after updating to -stable, and I've updated /usr/ports to -stable, but there are no instructions to do a build at the top of /usr/ports. Can I assume that would be because you generally don't want to build the whole ports tree? I'm reading the faq, and looks like pkg_add doesn't have any option to tell it whether to add from -stable or -current or -release . There are warnings not to mix packages from -stable and -current , and I think it at indicates not to mix -stable and -release . But I don't see any way to tell pkg_add which. It looks like pkg_add references and uses the ports directory, in which case it should know to get the -stable packages. Am I understanding things correctly? -- Joel Rees Be careful where you see conspiracy. Look first in your own heart, and ask yourself if you are not your own worst enemy.
Re: How does pkg_add know I'm tracking -stable?
joel.r...@gmail.com (Joel Rees), 2014.09.23 (Tue) 10:10 (CEST): I've built both /usr/src and /usr/xenocara after updating to -stable, and I've updated /usr/ports to -stable, but there are no instructions to do a build at the top of /usr/ports. Can I assume that would be because you generally don't want to build the whole ports tree? I'm reading the faq, and looks like pkg_add doesn't have any option to tell it whether to add from -stable or -current or -release . There are warnings not to mix packages from -stable and -current , and I think it at indicates not to mix -stable and -release . But I don't see any way to tell pkg_add which. It looks like pkg_add references and uses the ports directory, in which case it should know to get the -stable packages. Am I understanding things correctly? I think the following applies (pkg_add(1)): If the given package names are not found in the current working directory, pkg_add will search for them in each directory (local or remote) named by the PKG_PATH environment variable. If PKG_PATH is not defined, pkg_add will use the path named by installpath within pkg.conf(5). So _you_ decide by the path you specify. Bye, Marcus
Re: How does pkg_add know I'm tracking -stable?
* Joel Rees joel.r...@gmail.com [2014-09-23 10:12]: I've built both /usr/src and /usr/xenocara after updating to -stable, and I've updated /usr/ports to -stable, but there are no instructions to do a build at the top of /usr/ports. Can I assume that would be because you generally don't want to build the whole ports tree? pretty much. I'm reading the faq, and looks like pkg_add doesn't have any option to tell it whether to add from -stable or -current or -release . There are warnings not to mix packages from -stable and -current , correct and I think it at indicates not to mix -stable and -release . incorrect. -stbale is -release + fixes, the entire point of -stable is that it is 100% compatible with release - it just sees a few fixes. But I don't see any way to tell pkg_add which. pkg_add doesn't know or care about release/stable/current/frankenstein. The packages itself are built against a certain set of libraries and thus care (and pkg_add checks that). libraries don't change versions in -stable, pretty much by definition. to a smaller extent the same applies to syscalls and some other interfaces, but we get into nitpicking. you tell pkg_add a source for your packages, that's it. It looks like pkg_add references and uses the ports directory nope -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services GmbH, http://bsws.de, Full-Service ISP Secure Hosting, Mail and DNS. Virtual Dedicated Servers, Root to Fully Managed Henning Brauer Consulting, http://henningbrauer.com/
Re: How does pkg_add know I'm tracking -stable?
On Tue, Sep 23, 2014 at 5:34 PM, Henning Brauer hb-open...@ml.bsws.de wrote: * Joel Rees joel.r...@gmail.com [2014-09-23 10:12]: [...] and I think it at indicates not to mix -stable and -release . incorrect. -stbale is -release + fixes, the entire point of -stable is that it is 100% compatible with release - it just sees a few fixes. But I don't see any way to tell pkg_add which. pkg_add doesn't know or care about release/stable/current/frankenstein. The packages itself are built against a certain set of libraries and thus care (and pkg_add checks that). libraries don't change versions in -stable, pretty much by definition. to a smaller extent the same applies to syscalls and some other interfaces, but we get into nitpicking. you tell pkg_add a source for your packages, that's it. It looks like pkg_add references and uses the ports directory nope Thanks, Henning (and Marcus, too). That gets me straightened out. -- Joel Rees Computer storage is nothing but fancy paper, and the CPUs nothing but fancy pens. All is text, streaming from the past to the future forever.
