Date: Mon, 4 Dec 2006 16:31:06 -0500 From: Wesley Shields <wxs@atarininja.org> To: Doug Barton <dougb@FreeBSD.org> Cc: ports@freebsd.org, Robert Huff <roberthuff@rcn.com> Subject: Re: distfile belongs to? Message-ID: <20061204213106.GA42084@atarininja.org> In-Reply-To: <456B70E9.4030408@FreeBSD.org> References: <17771.24717.95357.989644@jerusalem.litteratus.org> <456B70E9.4030408@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 27, 2006 at 03:12:41PM -0800, Doug Barton wrote: > Robert Huff wrote: > > Let's suppose I have a list of tarballs > > (e.g. foobar-1.23.456.tar.gz). How do I tell which port each file > > belongs to? "pkg_info" only lists the end results. > > The correct answer is, "not easily." You can look at the code for > sysutils/portmaster to get an idea of how you could do it, but what > really needs to happen is for someone to write the code to embed that > data in the +CONTENTS file. I took a stab at this over the weekend. It's broken up into two parts. [1] is the addition to pkg_create and pkg_info and [2] is the addiction to bsd.port.mk. I mentioned this to pav@ on IRC a few days ago and I believe he and I may have miscommunicated regarding the use of this patch. With that said, I figured I would toss this out to the list as a possible way of recording the distfile(s) and patchfile(s) associated with a given port/package. The end result is a series of @distfile foo/bar.tar.gz lines in +CONTENTS. You can then use pkg_info -F to get a listing of them. It's my first time doing something like this so please be gentle. :) -- WXS [1]: http://www.atarininja.org/~wxs/patches/distfile-in-contents-part1.diff [2]: http://www.atarininja.org/~wxs/patches/distfile-in-contents-part2.diff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061204213106.GA42084>