Derek Jennings wrote:
On Monday 02 Jan 2006 09:58, Graham Watkins wrote:

Hi and Happy New Year to all,

It has just come to my attention that a new version of sane-backends has
just been released - 1.0.17-1.  However, the only rpms I can find are
made for Fedora.

Would using this be advisable or are there sound reasons why I should
hang on for a Mandriva version?

How long is the wait likely to be?


Cooker has 1.17-1 while 2006 Community has 1.16-5
You could either wait until Community is upgraded and install that, or else try the Cooker package. If it does not want to install without installing a gazillion dependencies then it would be safer to download the src.rpm and rebuild it.

I expect you will find drakxtools-newt is a dependency of sane-backends and you would need to rebuild that too. (drakxtools-newt contains the list of Mandriva supported scanners and the drakscanner GUI )

I would not use the Fedora package simply because it is not hard to get or make a Mandriva package.

I assume your scanner is not supported in the current version of sane or else there would be no point upgrading.

BTW: Some people may not be aware that the mirrors now carry a 'Community' version of Mandriva 2006. It is in the Mandriva-development folder on the mirrors. Example mirror ftp://ftp.rediris.es/pub/linux/distributions/mandrake-devel/community/

The community version is continuously updated once packages have been tested in Cooker. I would not suggest using community on a production server, but it is interesting if you want to be 'near', but not quite 'on' the bleeding edge. An snapshot iso of Community is now available to Mandriva club members as the 'Club December Distro'. Non members can upgrade online using urpmi if they wish.
derek

aren't these only 32bit versions? and not x86_64 arch?
____________________________________________________
Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com
Join the Club : http://www.mandrivaclub.com
____________________________________________________

Reply via email to