Sebastian: you screwed up the attributions. That makes things (more) confusing. Fix your MUA.
On Mon, Jun 19, 2006 at 05:10:21PM +0200, [EMAIL PROTECTED] wrote: > > You can do this the other way round, and make ports use packages > > where possible; see FETCH_PACKAGES in bsd.port.mk(5). > > Bad idea because the packages at $ANY_OFFICIAL_FTP are not > updated. Yes, they are. Packages are built for stable, too, if security updates are backported to the stable ports tree. What's the problem here? > That`s not what I ment as I said up2date. up2date for stables > means all Patches avaiable for stable. So if you use Stable but > curl *.1 except of *.3 you`re not up2date. :) That`s how I ment > it. What? I have no clue what you meant by this. Updated packages are bulit for stable when updates are backported. Period. Look at the updates[0] available for 3.9-stable. What's the problem here? > > Or if you have enough systems using the same arch for it to be > > worthwhile, you can build your own packages and point PKG_PATH > > there. > > Well at home 1 AMD64 and 3 i386 (even just 2 of 3 use OpenBSD). I > just wanted to point out that with pkg_add -ui there`s a VERY GOOD > solution but even the best solution is useless if the packages > don`t get updated. Maybe that can get solved with a Script *looks > to the dev-Team* to update the packages on the FTP if a update is > avaiable via Ports. This happens already[0]. > Or, the other solution, would be enable pkg_add -ui (maybe with > another argument to use Ports) using the Port-system to update. > It`s not so easy to update all machines using the ports.... Easy > == like pkg_add -ui :-/ So, assuming there's no package available, just make the package (ports(7)) and install it on other machines with the same arch (like Stuart suggested). Or add your build machine to your other machines' PKG_PATH. It's easy. But chances are, there's an updated package available. Don't expect new features if you're running -stable. > That`s all I wanted to point out. Why not using this neat > update-tool (pkg_add -ui) because for now the dev-team limits it > to a "upgrade"-tool (from one release to another) except an > update-tool. And that`s kind of sad in my oppinion. Again, this is unclear. But pkg_add handles upgrades _and_ updates. If you're running -stable, you might not notice many package updates, since that'll only happen when a new package is built to address a security problem. If you want more packages to be built faster, submit diffs to update the ports you're concerned with, donate resources for a larger build infrastructure, or build your own packages. [0]http://www.openbsd.org/pkg-stable.html -- o--------------------------{ Will Maier }--------------------------o | jabber:[EMAIL PROTECTED] | [EMAIL PROTECTED] | | freenode:..............lt_kije | freenode:........#madlug,#wilug | *------------------[ BSD Unix: Live Free or Die ]------------------*
