Hello,
sounds like you want to build a SUBDIRLIST with pkg_info(1).
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Thanks for the advise. I found a very easy solution to do that:
PLIST=$(mktemp)
/usr/ports/infrastructure/build/out-of-date > $PLIST
cd /usr/ports/
SUBDIRLIST=$
On Tue, Dec 12, 2006 at 07:29:45PM +0100, fv wrote:
> >pkg_add -ui does what you want to do. (No, it doesn't go to ports, but
> >you shouldn't, especially not if you must ask how to do this.)
>
> I just would like to maintain a local up-to-date package database
> compiled from ports so i can dot p
fv [2006-12-12, 19:29:45]:
> >pkg_add -ui does what you want to do. (No, it doesn't go to ports, but
> >you shouldn't, especially not if you must ask how to do this.)
> >
> > Joachim
> >
> I just would like to maintain a local up-to-date package database
> compiled from ports so i can
pkg_add -ui does what you want to do. (No, it doesn't go to ports, but
you shouldn't, especially not if you must ask how to do this.)
Joachim
I just would like to maintain a local up-to-date package database
compiled from ports so i can dot periodicaly:
PKG_PATH=/usr/ports/pack
On Tue, Dec 12, 2006 at 01:31:31PM +0100, Francois Visconte wrote:
> Hello,
> I'm searching for a way to automaticaly doing the following actions:
> 1/ update port tree (OPENBSD_4_0)
> 2/ get installed packages and find corresponding ports
> 3/ build this packages from ports.
>
> Maybe i missed th
Hello,
I'm searching for a way to automaticaly doing the following actions:
1/ update port tree (OPENBSD_4_0)
2/ get installed packages and find corresponding ports
3/ build this packages from ports.
Maybe i missed the point but i don't find an existing way to do that.
I'm using the following way
6 matches
Mail list logo
