Re: [proaudio] CLAM: =libclam-9999 and =NetworkEditor-9999 patch |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] CLAM: =libclam-9999 and =NetworkEditor-9999 patch
- From: Natanael Olaiz <nolaiz@xxxxxxxxx>
- Date: Fri, 21 Jan 2011 10:28:23 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:x-enigmail-version:openpgp :content-type:content-transfer-encoding; bh=1/rcllmkkQZcfWawwkdx4jvXevjqCvEGLvsB+onxxtQ=; b=h3NZNr2kzzvS0+dcdNSLVS5BiS8g9gMaq8AIATu7Ui5vGE/vi6WDdUMkaZCyLGfyD8 LtfDJQe3MHpNxDkWP0ce/iDS3zGgm2H7sByUzdrYw6nD0H1oj3ccpSpc7/65xBTaRuo2 5klL5d1dmpgHJIUVptbmilSSkqTNeR79qSFiU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=XjKDp/1wxvdJHqvNlih5j4rjLOc874hDp6XIghuB2nk7p1sTiYftoAhVMYQfs1DOyP +LvSA2Twmk5sWoDhlWGqJ07+qiDPRlBGs07DSWTHKmvbYUNGclp0XbZ6EKtWq3/1d7dA e0eUK7qmZ3nIWu/M8socuM6vFQzR83EP22Lkw=
- Openpgp: id=BF073DBC
I see that the logic to set the xmlbackend was inverted! (that is the
reason because doesn't compile with -xercesc if you don't have it :) )
+ if ! use xercesc; then
+ myconf="${myconf} xmlbackend=xercesc"
+ else
+ myconf="${myconf} xmlbackend=xmlpp"
+ fi
I'll do some tests, copy the 1.4.0 ebuild logic (to allow the 4
combinations) and send a new patch.
Best regards,
Natanael
El 01/20/11 22:17, Viktor Lazarev escribió:
> Hi Natanael,
>
> Regarding to XML backend:
> libclam-9999 doesnt compile with USE="-xercesc" (I have installed
> xmlpp-1.0.5). If compare 9999 & 1.4.0, it can be seen that 1.4.0
> already contains lines:
>
> .....
> IUSE="some_use_flags xercesc +xmlpp"
> .....
> RDEPEND="some_depends
> xercesc? ( <dev-libs/xerces-c-3 )
> xmlpp? ( dev-cpp/libxmlpp:2.6 )
> "
> .....
> src_compile() {
> .....
> if use xercesc; then
> if use xmlpp; then
> myconf+=" xmlbackend=both"
> else
> myconf+=" xmlbackend=xercesc"
> fi
> else
> if use xmlpp; then
> myconf+=" xmlbackend=xmlpp"
> else
> myconf+=" xmlbackend=none"
> fi
> fi
> }
>
> also Sconstruct of svn-version contains:
> opts.Add( EnumVariable( 'xmlbackend', 'XML passivation backend',
> 'xercesc', ('xercesc','xmlpp','both','none')) )
>
> So, I guess live-ebuild should contains the same lines.
> And one question: which xmlbackend is more preffered? As you can see,
> in 1.4.0 it is xmlpp, is it right?
>
> 2011/1/20, Natanael Olaiz <nolaiz@xxxxxxxxx>:
>> Hi,
>>
>>
>> Here is a patch for =media-libs/libclam-9999 (-r1) and
>> =media-sound/NetworkEditor-9999
>>
>> I'm a CLAM developer since a few years, but I'm a pretty new using
>> Gentoo, so probably the ebuilds are not very good... but at least: I
>> made libclam and NetworkEditor live ebuilds works!
>>
>> See attached changelogs for the changes.
>>
>>
>> One of these days I'll check the release versions of the ebuilds, and
>> the SMSTools, Annotator, Voice2MIDI and chordata... Meanwhile, all
>> suggestions are welcome (I'm learning about the ebuilds and the portage
>> system).
>>
>>
>> And last but not least: thank you all for your work with the overlay!
>>
>>
>> Best regards,
>> Natanael.
>>
>