On Sat, Jul 03, 2010 at 06:53:07PM +0200, Toni Mueller wrote:
> On Fri, 02.07.2010 at 12:27:27 +0100, Stuart Henderson <[email protected]> 
> wrote:
> > Sorry reports from 4.7 are not too helpful here for this. If it
> > happens for anyone on -current, please capture full build logs -
> 
> I'm aware that the project may not have that much of an interest in
> looking at this, but it's imho a problem I as a user has.

If you're trying to use a current ports tree on a -stable system,
you can't expect any help from anyone. Saem for testing/trying diffs
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.

> 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)).

But note that out-of-date also needs to be in sync with the pkg_tools
in base.

> As there are no package repositories for -current,

${YOUR_FAVORITE_MIRROR}/pub/OpenBSD/snapshots/packages/${MACHINE_ARCH}/

(yes, amd64 is outdated, no idea why)

Ciao,
        Kili

Reply via email to