Hi, there seems to be some kind of misunderstanding about what I consider to be the problem, and what you think what I'm doing.
On Sat, 03.07.2010 at 22:49:19 +0200, Matthias Kilian <[email protected]> wrote: > If you're trying to use a current ports tree on a -stable system, To clarify: I'm not using a -current ports tree on a -stable system, I'm trying to update single port to -current and build it with the -stable ports infrastructure and other packages from -stable, as far as I can go. In many cases, this works just fine. I'm fully aware that a -current ports tree may contain a lot of other changes, besides a new port of the XY software, too, and try to work around this, and that esp. the infrastructure part doesn't mix well (or at all) with a -stable system. > you can't expect any help from anyone. Umm... Marc's response made it very clear that a user of ports or packages is mostly out in the dust. I didn't expect much else, anyway, but this is one of OpenBSD's real weaknesses, as there is no security support for ports nor packages, and I think we should be able to agree upon the idea that expecting OpenBSD users to wait for about half a year until they can fix up their system is beyond reason. This has been a problem in OpenBSD for quite some time, too. Getting security updates, eg. recently for nginx (0.7.65 -> 0.7.67) is one such case where I work this idea. Usually, running a "cvs up -PAd ." in the affected ports directory is sufficient to get a desirable update, but sometimes it doesn't work - eg. in this case, with Python. I don't know what else I can do to when I hit a problem, except for rolling up my own sleeves and/or mailing this list, which I do both. > sent to this mailinglist. It's annoying, but we can't avoid it. If > we start to keep the ports tree working on -stable (or even older > releases), there will be no more improvements to bsd.port.mk nor > to pkg_add & friends. I fully understand that the project is understaffed to handle this case. I'm not happy if nobody helps me out, but I do find Marc's response _unreasonable_. > > Is there an easy way to discover which packages are outdated and in > > need to be rebuilt? > > /usr/ports/infrastructure/build/out-of-date creates output suitable > to be used for SUBDIRLIST (see ports(7)). Great, thanks! > > As there are no package repositories for -current, > ${YOUR_FAVORITE_MIRROR}/pub/OpenBSD/snapshots/packages/${MACHINE_ARCH}/ > (yes, amd64 is outdated, no idea why) Ok, I'll have to dig into this. Now I only need a way to get to a sane auto-naming scheme. With -stable systems, I construct the URLs to packages using `uname -m` and `uname -r`, but with any -current system, this breaks down... -- Kind regards, --Toni++
