ports with bad plist when NO{DOCS,EXAMPLES,PORTDATA} defined

Jeremy Messenger mezz7 at cox.net
Mon May 19 21:43:23 UTC 2008


On Mon, 19 May 2008 16:07:59 -0500, Ion-Mihai Tetcu <itetcu at FreeBSD.org>  
wrote:

> On Mon, 19 May 2008 15:49:42 -0500
> "Jeremy Messenger" <mezz7 at cox.net> wrote:
>
>> On Mon, 19 May 2008 15:31:59 -0500, Ion-Mihai Tetcu <itetcu at FreeBSD.org>
>> wrote:
>>
>> > On Mon, 19 May 2008 15:17:28 -0500
>> > "Jeremy Messenger" <mezz7 at cox.net> wrote:
>> >
>> >> On Mon, 19 May 2008 13:50:10 -0500, Ion-Mihai Tetcu  
>> <itetcu at FreeBSD.org>
>> >> wrote:
>  [ .. ]
>> >> > This is the list of ports that fail and their maintianers:
>> >>
>> >> > graphics/ruby-cairo - mezz at FreeBSD.org
>> >> > graphics/cairomm - gnome at FreeBSD.org
>> >> > devel/glibmm-reference - gnome at FreeBSD.org
>> >>
>> >> Fixed, thanks for setup tinderbox and report!
>> >
>> > Thanks, you're the first, followed closely by garga@ (but you fixed 3
>> > ports).
>>
>> I am hoping to modify or rewrite our (FreeBSD GNOME Team) reference
>> framework in someday.
>>
>> > The test (for all 4 NO* vars) is automated now after each commit, but
>> > the emails I'll be sending out manually to catch false positives.
>> >
>> > Let's hope my hardware can keep up with the commits :)
>> > (which I doubt for large commits, but I'm building an other tindy).
>>
>> What are you planning to use another tinderbox?
>
> I have now a i386 tindy and an amd64 one. The second one will be also an
> amd64, close enough to the first one I hope (if things go right and I
> can have a low-latency fiber between them) to be able to nfs-mount the
> pkg dir, to speed-up things. This devel/* build took almost a week
> (started with a fresh ports tree, nothing build in it).
>
> If things go right with the two deals we're negotiating @work maybe I
> can shanghai a third box and offer some cycles like droso's tindys.
>
> BTW, what's GNOME Team's infrastructure now?

If tarball has reference[1] then we sometime use reference framework  
(USE_GNOME=referencehack in master port and include  
devel/glib20-reference/bsd.gnome-reference.mk in slave port). I don't  
really like current reference framework because it's complicate than what  
it is supposed to be and portlint doesn't work with it. Also, the  
*-reference ports shouldn't have NOPORTDOCS option. Other than reference,  
we use normal like other ports.

[1] The references contain the Application Programming Interface, list of  
functions, classes and methods of the GNOME platform libraries and the  
standards used within the GNOME platform.  
http://library.gnome.org/devel/references

Cheers,
Mezz


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


More information about the freebsd-gnome mailing list