Best way of patching sources for changed libbeagle?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I need some help with the new libbeagle-0.3.0. This one is listed in 
pkg-config with "libbeagle-1.0". The configure script of kerry (and also 
brasero and yelp) are explicit checking for "libbeagle-0.0". 
Upstream hasn't catched up the new beagle, yet, so I have to figure out what 
is the best way of preparing my package (kerry) for the new libbeagle 
version. And here I need some help because I'm not very familiar with 
configure scripts. :)

My attempt here is to avoid a patch and change the libbeagle version with sed:

> %build
> unset QTDIR || : ; . /etc/profile.d/qt.sh
> export QTLIB=${QTDIR}/lib QTINC=${QTDIR}/include
>
> # libbeagle-version is now 0.1
> sed -i
> 's/LIBBEAGLE_PACKAGES="libbeagle-0.0"/LIBBEAGLE_PACKAGES="libbeagle-1.0"/' 
> configure
>
> %configure --disable-rpath --disable-debug
> make %{?_smp_mflags}


A scratch build seems to be fine:
http://koji.fedoraproject.org/koji/taskinfo?taskID=285293


But I think there would be better options to to this.

Sebastian

Attachment: signature.asc
Description: This is a digitally signed message part.

--
Fedora-packaging mailing list
Fedora-packaging@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-packaging

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux