Date: Wed, 22 Jun 2005 11:28:44 -0700 (PDT) From: "Casey Scott" <casey@phantombsd.org> To: =?iso-8859-1?Q?Bj=F6rn_K=F6nig?= <bkoenig@cs.tu-berlin.de> Cc: Casey Scott <casey@phantombsd.org>, Dan Nelson <dnelson@allantgroup.com>, freebsd-questions@freebsd.org Subject: Re: pkg_info question Message-ID: <16618.199.181.134.212.1119464924.squirrel@mail.phantombsd.org> In-Reply-To: <42B9AA56.7010907@cs.tu-berlin.de> References: <12654.199.181.134.212.1119458656.squirrel@mail.phantombsd.org> <20050622165027.GB49171@dan.emsphone.com> <29955.199.181.134.212.1119460796.squirrel@mail.phantombsd.org> <42B9AA56.7010907@cs.tu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks. Good idea. How about this, its a little easier. #find ./ -name 'pkg-plist*' | xargs grep 'bin/convert' Casey > Casey Scott wrote: > >> Sorry, I meant I need to know what package a file belongs to that does >> not >> exist in the file system already. I need to know where to get something, >> not where it came from. > > My CVSup script executes > > find /usr/ports -name "pkg-plist*" > /path/to/somewhere > > after an update of the ports directory. Thus I can search a file with > > cat /path/to/somewhere | xargs grep 'pattern' > > This method is quick and dirty and does not cover all ports because some > of them have no pkg-plist file in their directory. Those ports use the > PLIST_FILES variable in their Makefile instead or generate a plist file > dynamically. > > Björn > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16618.199.181.134.212.1119464924.squirrel>