On Thu, May 23, 2002 at 04:34:18AM -0000, Moshe Zadka wrote:
>
> > 1a) as 1), but also provide foo symlink for python (default).
>
> this makes sense....I can just put the symlink in python2.1-foo-bin and
> move the symlinks when a python default change.
Or you can use the update-alternatives tool we have and leave to it the
task of doing the symlink, so you can provide:
- python2.1-foo
- python2.2-foo
- ...
- pythonX-Y-foo
each one with a /usr/bin/foo-X.Y symlinked (through alternatives) by
/usr/bin/foo. No need then for pythonX.Y-foo-bin if you don't want it.
That also ensures your users will be able to install _both_ versions and
to decide which 'binary' use as the default, while still being able to
run the other by it's full name if they want.
Regards,
Ricardo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
