3 ms·

Cool! Thanks for correcting me. That said: I need more stuff than the ports tree contains (I .. checked NetBSD and FreeBSD, plus a couple of Linux distribution

Cool! Thanks for correcting me. That said: I need more stuff than the ports tree contains (I .. checked NetBSD and FreeBSD, plus a couple of Linux distributions. I admit that I haven't checked all my packages against OpenBSD's ports tree, but I assume I'm correct). Plus, I do need the occasional update without waiting 6 month. How would I do that? For comparison: On FreeBSD I use portshaker to create a ports tree that is a mixture of upstream (FreeBSD) and other sources (a git repository, in my case). If FreeBSD doesn't bump a package and PRs take a whiiiiile, I bump that thing in my overlay. poudriere allows me to build (in bulk) all my relevant packages in jails, is clever enough to rebuild just the stuff that changed (or where I changed the config) and spits out a directory structure that represents a pkgng repository with (optional) signed binary packages. pkgng is pointed to my repository (actually it supports multiple sources, apt like. Can PKG_PATH do that?), which contains now builds from upstream ports and my overlay. How would I (hoping that you have a couple of minutes and can prove me wrong once more) - build binary packages for ports that either don't exist upstream (stuff I ported) or are outdated upstream? - distribute those in a decent way (PKG_PATH swapping..?) I guess I'm left with the question whether we're talking about the same thing when we're saying 'decent binary packages'? I'm sure you can OpenBSD works well for the intended use - but 'decent' wasn't an objective attribute here, it was more a subjective 'decent for my needs' kind of thing. More details above. In the end, pkg_* feel like ooold Solaris, or like using Slackware again. That's package management on a different level and feels like a step down from apt/yum/pacman/pkgng. Again: Probably it's just a matter of convenience and my laziness in the end, but so far I feel that's not for me.

avsm 13y ago
I'll just point you at the ports and packages documentation, which has answers to all your questions: http://www.openbsd.org/faq/faq15.html http://www.openbsd.org/faq/faq15.html
- darklajid 13y ago
  Fair enough. Here's an upvote, that's probably the right answer. That said: I read that page. Multiple times. It doesn't help me mapping my portshaker/poudriere setup into something in the OpenBSD world so far. On the other hand: It makes no sense to expect that answer from you either, so .. back to the first line, full circle. :)
clarry 13y ago
I should note that most OpenBSD users don't like needless tinkering and therefore stick to the binary packages. Those who want more up to date packages run a -current snapshot. Stable packages are also available via M:Tier. But if you want to tinker and build your packages, you can do that. That's what the ports tree is there for. That is how the OpenBSD packages are built. > - build binary packages for ports that either don't exist upstream (stuff I ported) or are outdated upstream? The package target for bsd.port.mk(5): package Build a port package (or packages in a MULTI_PACKAGES case) from the fake installation. Involves creating packaging information from templates (see COMMENT, SUBST_VARS among others) and invoking pkg_create(1) for each package in the MULTI_PACKAGES list. If the repository already contains up-to-date packages, they are not rebuilt. > - distribute those in a decent way (PKG_PATH swapping..?) It is very easy to distribute OpenBSD packages. You can use http, ftp, nfs.. Yes, PKG_PATH needs to be set, just like you need to configure the package manager to your own repo on any other system. > actually it supports multiple sources, apt like. Can PKG_PATH do that? pkg_add(1): PKG_PATH If a given package name cannot be found, the directories named by PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name. URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. The current directory may be indicated implicitly by an empty directory name, or explicitly by a single period (`./'). > poudriere allows me to build (in bulk) all my relevant packages in jails So OpenBSD doesn't have jails, but it is possible to do ports builds from a read-only ports tree using a non-privileged user, with systrace in place to filter accesses that shouldn't happen. > In the end, pkg_* feel like ooold Solaris, or like using Slackware again. That's package management on a different level and feels like a step down from apt/yum/pacman/pkgng. You sure have lots of feelings about a package manager you don't know. Have you even used it? I haven't used pkgng and my experience with yum & pacman is limited, but apt (and aptitude) is what made me finally quit using Linux; I'm 100% OpenBSD now. pkg_add is a definite step up for me, whether using subjective feelings or the number of times it's broken things for me as the metric.
- darklajid 13y ago
  Hey. I appreciate the help people are offering here. I'm building a list of links (currently the Porter's handbook and various links around that) to read and decided that I need to dive deeper, give it a real spin (again) before commenting .. again. If I understand the first part of your answer, or where it is coming from: I .. do understand that I can create packages. I don't understand how I'd have my own ports tree in a sensible way (do you have a couple of trees? Build package A from here, package B from there?), when you need stuff that just isn't ported/too 'niche'. Or if you need to bump a version of a port that is in the official tree. I knew about make package, see above (same on/similar to systems I use today). I posted my new understanding about PKG_PATH elsewhere in this thread, but I guess I DO have to admit that I should've hit the man page first. Admittedly I never used it for more than pointing to one single official mirror in the couple of VMs I played with. Anyway: Cool. I'm not married to jails, I just like that poudriere offers a very nice way to build packages in an isolated environment. Security isn't the biggest concern here: One thing that this allows me to do for example is to run one version of FreeBSD and build packages in a jail of another version (or another arch, or both). At this point I assume there's an OpenBSD equivalent for this functionality as well though. :) My feelings about pkg_* are honestly based on older experiences with FreeBSD and recent but discontinued explorations in NetBSD. My last OpenBSD installation is a while back and I might've given up quite quickly. Which of course might entirely be a fault of my character. No offense intended, if you feel I attacked either you or a project you sympathize with I'm sorry about that.

avsm 13y ago

I'll just point you at the ports and packages documentation, which has answers to all your questions: http://www.openbsd.org/faq/faq15.html http://www.openbsd.org/faq/faq15.html

darklajid 13y ago
Fair enough. Here's an upvote, that's probably the right answer. That said: I read that page. Multiple times. It doesn't help me mapping my portshaker/poudriere setup into something in the OpenBSD world so far. On the other hand: It makes no sense to expect that answer from you either, so .. back to the first line, full circle. :)

clarry 13y ago

I should note that most OpenBSD users don't like needless tinkering and therefore stick to the binary packages. Those who want more up to date packages run a -current snapshot. Stable packages are also available via M:Tier. But if you want to tinker and build your packages, you can do that. That's what the ports tree is there for. That is how the OpenBSD packages are built. > - build binary packages for ports that either don't exist upstream (stuff I ported) or are outdated upstream? The package target for bsd.port.mk(5): package Build a port package (or packages in a MULTI_PACKAGES case) from the fake installation. Involves creating packaging information from templates (see COMMENT, SUBST_VARS among others) and invoking pkg_create(1) for each package in the MULTI_PACKAGES list. If the repository already contains up-to-date packages, they are not rebuilt. > - distribute those in a decent way (PKG_PATH swapping..?) It is very easy to distribute OpenBSD packages. You can use http, ftp, nfs.. Yes, PKG_PATH needs to be set, just like you need to configure the package manager to your own repo on any other system. > actually it supports multiple sources, apt like. Can PKG_PATH do that? pkg_add(1): PKG_PATH If a given package name cannot be found, the directories named by PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name. URL schemes such as FTP, HTTP, HTTPS, or SCP are also appropriate. The current directory may be indicated implicitly by an empty directory name, or explicitly by a single period (`./'). > poudriere allows me to build (in bulk) all my relevant packages in jails So OpenBSD doesn't have jails, but it is possible to do ports builds from a read-only ports tree using a non-privileged user, with systrace in place to filter accesses that shouldn't happen. > In the end, pkg_* feel like ooold Solaris, or like using Slackware again. That's package management on a different level and feels like a step down from apt/yum/pacman/pkgng. You sure have lots of feelings about a package manager you don't know. Have you even used it? I haven't used pkgng and my experience with yum & pacman is limited, but apt (and aptitude) is what made me finally quit using Linux; I'm 100% OpenBSD now. pkg_add is a definite step up for me, whether using subjective feelings or the number of times it's broken things for me as the metric.

darklajid 13y ago
Hey. I appreciate the help people are offering here. I'm building a list of links (currently the Porter's handbook and various links around that) to read and decided that I need to dive deeper, give it a real spin (again) before commenting .. again. If I understand the first part of your answer, or where it is coming from: I .. do understand that I can create packages. I don't understand how I'd have my own ports tree in a sensible way (do you have a couple of trees? Build package A from here, package B from there?), when you need stuff that just isn't ported/too 'niche'. Or if you need to bump a version of a port that is in the official tree. I knew about make package, see above (same on/similar to systems I use today). I posted my new understanding about PKG_PATH elsewhere in this thread, but I guess I DO have to admit that I should've hit the man page first. Admittedly I never used it for more than pointing to one single official mirror in the couple of VMs I played with. Anyway: Cool. I'm not married to jails, I just like that poudriere offers a very nice way to build packages in an isolated environment. Security isn't the biggest concern here: One thing that this allows me to do for example is to run one version of FreeBSD and build packages in a jail of another version (or another arch, or both). At this point I assume there's an OpenBSD equivalent for this functionality as well though. :) My feelings about pkg_* are honestly based on older experiences with FreeBSD and recent but discontinued explorations in NetBSD. My last OpenBSD installation is a while back and I might've given up quite quickly. Which of course might entirely be a fault of my character. No offense intended, if you feel I attacked either you or a project you sympathize with I'm sorry about that.