Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 03 Nov 2005 21:01:54 -0600
From:      "Jeremy Messenger" <mezz7@cox.net>
To:        "Adam Weinberger" <adamw@freebsd.org>
Cc:        cvs-ports@freebsd.org, Kris Kennaway <kris@freebsd.org>, cvs-all@freebsd.org, ports-committers@freebsd.org
Subject:   Re: cvs commit: ports/deskutils/gourmet Makefile
Message-ID:  <op.szo31gid9aq2h7@mezz.mezzweb.com>
In-Reply-To: <436ACB61.5070703@FreeBSD.org>
References:  <200511040013.jA40D0Eb043334@repoman.freebsd.org> <436ACB61.5070703@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 03 Nov 2005 20:45:53 -0600, Adam Weinberger <adamw@FreeBSD.org>  
wrote:

> Kris Kennaway wrote:
>> kris        2005-11-04 00:13:00 UTC
>>    FreeBSD ports repository
>>    Modified files:
>>     deskutils/gourmet    Makefile   Log:
>>   BROKEN: Incomplete pkg-plist
>>     Revision  Changes    Path
>>   1.12      +2 -0      ports/deskutils/gourmet/Makefile
>
> Kris -
>
> Per our previous discussion about this, this port isn't broken. When  
> another app uses metakit's python library, a byte-compiled version of  
> the library is created. The file in question gets created by python  
> during the gourmet build. Such a file technically belongs to metakit,  
> and is handled as best I could think of in rev 1.19 of  
> databases/metakit/pkg-plist.

It sounds like you might need to add a manual run compileall.py in  
post-install target in metakit to create that .pyc file. I had to deal  
with that in a few ports such as smeg, gdesklets and etc.

Cheers,
Mezz

> Unless you really feel that deinstalling gourmet should remove the file  
> instead of when deinstalling metakit, I'd like to request that you  
> back-out the BROKENness.
>
> # Adam


-- 
mezz7@cox.net  -  mezz@FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.szo31gid9aq2h7>