Re: backporting
Rob Weir wrote:
On Mon, Feb 10, 2003 at 05:27:54PM +0000, Sean Burlington wrote:
I needed a newer version of sane to support my scanner and ended up
backporting the sane packages from unstable to testing
but as its the forst time I have done this sort of thing I just want to
ask - have I done this a sensible way ?
[snip]
Am I likely to have broken anything by modifying the configure script
without changing the package version ? (if so - how do I change the
package version)
No. The worst case is that apt decides it likes Debian's packages more
than yours and tries to 'upgrade' it to whatever it sees on your mirror.
You can avoid this by bumping the version number, but since it seems the
point of this was to get a newer version, you should be fine.
yeah - I wouldn't have any complaints about apt installing the officail
version over mine
all comments welcome - I've only been using debian for a few weeks
having migrated fron redhat.
Wow, impressive :) Two weeks from newbie to package backporter :)
the things you can do when you're in between jobs ...
and I have been using Linux for around 5 years now - so I'm maybe not
your typical newbie ;)
So far its goping OK - but there are a few packages where I really need
more up-to date versions.
Yeah, that's true. Try apt-get.org for lots of other backports and
unofficial packages; you might even want to list your packages there.
I've had a look there but not found the things I wanted
BUT - now I look again and find the sane packages have already been
backported !!!
I was looking for the original package names of
sane-frontends
sane-backends
but the debian packages become
libsane
libsane-dev
libsane-extras
libsane-extras-dev
sane
sane-gimp1.2
sane-utils
oh well - thats the price of unfamiliarity !
still I learned some usefull stuf :)
my next project will be to have a look at backporting gnomemeeting -
which could be more trivky as the unstable package has heaps of
dependancies from gnome2
thanks for your comments
--
Sean
Reply to: