Thanks for your answer,
I used the source package of Michael and modified the debian/control
file according to the librairies available on my (dapper) system.
Actually the only changes I had to make were:
downgrading version of
dpkg-dev from (>= 1.13.19) to (>= 1.13.11)
libglib2.0-dev from (>= 2.12.0) to (>= 2.10.3)
renaming library libgmime-2.0-2-dev (>= 2.1.0) to libgmime2.1-dev
(>=2.1.0) -- this actually looked strange!
and replacing the ${shlibs:Depends}, ${misc:Depends} that resolves to
libc6 (>= 2.4-1), libdbus-1-3, libdbus-glib-1-2 (>= 0.71), libglib2.0-0
(>= 2.12.0)
by
libc6 (>= 2.3.6), libdbus-1-2, libdbus-glib-1-2 (>= 0.60), libglib2.0-0
(>= 2.10.3)
(mostly because calling "debuild -us -uc" didn't knew the variables
above... help for fixing this is highly welcome!)
So I guess my only trouble might come from these packages using
libdbus-1-2 instead of 1-3... is there any REAL requirement for 1-3 in
current tracker? if so I could have a look at providing a backport for
this one too... eventually.
Would you mind telling me if the attached packages are of "satisfactory"
quality... or how I should improve them... and eventually adding them to
the repository?
Bertrand.
Michael Biebl a écrit :
2007/1/9, B Berteh <berteh hotmail com>:Could you please build tracker packages for dapper... or eventually provide me with the debian/ directory (controls, rules...) you used so that I can try building it by myself?I don't intend to provide dapper packages, simply because there are several unsatisfied build dependencies on dapper, and I lack the time to maintain workarounds for that.
_________________________________________________________________Saviez-vous que Windows Live Messenger est disponible dès maintenant sur votre GSM ? http://get.live.com/messenger/mobile
Attachment:
tracker-0.5.3_dapper_packages.tar.bz2
Description: Binary data