Date: Wed, 17 May 2006 16:58:09 -0400 From: "michael johnson" <ahze@ahze.net> To: "Dan Langille" <dan@langille.org> Cc: gnome@freebsd.org Subject: Re: ports without pkg-descr Message-ID: <b2203fed0605171358u4d2cb83jb4ddc0d20337dd87@mail.gmail.com> In-Reply-To: <446B41E3.9161.A355435@dan.langille.org> References: <446B41E3.9161.A355435@dan.langille.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/17/06, Dan Langille <dan@langille.org> wrote: > > Hi folks, > > I'm having trouble understanding a few ports and I'm hoping you can > help. The ports in question are: > > devel/glib20-reference > devel/glibmm-reference > > The issue: pkg-descr, or more precisely, the output of make -V DESCR. > > [dan@polo:/usr/home/dan/ports/devel/glibmm-reference] $ make -V DESCR > /usr/home/dan/ports/devel/glibmm-reference/work/pkg-descr > > Is that expected? A pkg-descr in the working directory? pkg-descr added to ports, thanks! If so, that file is created during the build process. Within the > current FreshPorts framework, this is an anomoly and there is no way > for the system to go through the steps necessary to create that file. > > I have attempted to make both devel/glibmm-reference and and still > not find a pkg-descr file. Is this expected behaviour? > > Is is really necessary to have a pkg-desc that is constructed > automatically? I ask in case there's a way around this without > special casing it for FreshPorts. > > Thanks. > > > > > > -- > Dan Langille : Software Developer looking for work > my resume: http://www.freebsddiary.org/dan_langille.php > > > _______________________________________________ > freebsd-gnome@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b2203fed0605171358u4d2cb83jb4ddc0d20337dd87>