public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@gentoo.org>
To: Donnie Berkholz <dberkholz@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-tv/mythtv:  ChangeLog mythtv-0.20.2_p14668.ebuild mythtv-0.21_pre14666.ebuild  mythtv-0.21_pre14480-r1.ebuild
Date: Sun, 14 Oct 2007 00:12:59 -0400	[thread overview]
Message-ID: <4711974B.6010505@gentoo.org> (raw)
In-Reply-To: <20071013004453.GM23990@supernova>

Donnie Berkholz wrote:
> On 18:55 Fri 12 Oct     , Doug Goldstein (cardoe) wrote:
>   
>> 1.1                  media-tv/mythtv/mythtv-0.20.2_p14668.ebuild
>>
>> file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/media-tv/mythtv/mythtv-0.20.2_p14668.ebuild?rev=1.1&view=markup
>> plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/media-tv/mythtv/mythtv-0.20.2_p14668.ebuild?rev=1.1&content-type=text/plain
>>     
>
>   
>> 	use alsa || myconf="${myconf} --disable-audio-alsa"
>> 	use jack || myconf="${myconf} --disable-audio-jack"
>> 	use dts || myconf="${myconf} --disable-dts"
>> 	use freebox || myconf="${myconf} --disable-freebox"
>> 	use dbox2 || myconf="${myconf} --disable-dbox2"
>> 	use hdhomerun || myconf="${myconf} --disable-hdhomerun"
>> 	use crciprec || myconf="${myconf} --disable-crciprec"
>> 	use altivec || myconf="${myconf} --disable-altivec"
>> 	use xvmc && myconf="${myconf} --enable-xvmc"
>> 	use xvmc && use video_cards_via && myconf="${myconf} --enable-xvmc-pro"
>> 	use perl && myconf="${myconf} --with-bindings=perl"
>> 	myconf="${myconf}
>> 		--disable-audio-arts
>> 		$(use_enable lirc)
>> 		$(use_enable joystick joystick-menu)
>> 		$(use_enable dvb)
>> 		--dvb-path=/usr/include
>> 		$(use_enable opengl opengl-vsync)
>> 		$(use_enable ieee1394 firewire)
>> 		--enable-xrandr
>> 		--enable-xv
>> 		--disable-directfb
>> 		--enable-x11
>> 		--enable-proc-opt"
>>     
>
> How come some of these don't use use_enable()?
>   
Because if you pass the inverse the script blows up. It's ffmpeg's 
configure script that's a hand written script and modified by the MythTV 
developers.

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-10-14  4:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1IgPfK-0005R4-Tw@stork.gentoo.org>
2007-10-13  0:44 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-tv/mythtv: ChangeLog mythtv-0.20.2_p14668.ebuild mythtv-0.21_pre14666.ebuild mythtv-0.21_pre14480-r1.ebuild Donnie Berkholz
2007-10-14  4:12   ` Doug Goldstein [this message]
2007-10-14  4:50     ` Donnie Berkholz
2007-10-14 12:02       ` [gentoo-dev] " Steve Long
2007-10-15 14:16       ` [gentoo-dev] " Doug Goldstein
2007-10-15 14:25         ` Jonathan Adamczewski
2007-10-15 14:37           ` Doug Goldstein
2007-10-15 18:31             ` Christian Faulhammer
2007-10-15 21:00               ` Doug Goldstein
2007-10-16 10:09                 ` Marijn Schouten (hkBst)
2007-10-15 19:14             ` Alec Warner
2007-10-15 20:57               ` Doug Goldstein
2007-10-15 22:09                 ` Donnie Berkholz
2007-10-16  1:17                 ` Ryan Hill
2007-10-16 23:04               ` Drake Wyrm
2007-10-15 20:57         ` [gentoo-dev] " Steve Long

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4711974B.6010505@gentoo.org \
    --to=cardoe@gentoo.org \
    --cc=dberkholz@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox