[Pkg-crosswire-devel] links to modules was Re: Debconf question to install modules and other ideas

[Daniel Glassey]

On Tue, Jan 27, 2009 at 6:51 AM, Eeli Kaikkonen
<eekaikko at mail.student.oulu.fi> wrote:
> Quoting Daniel Glassey <dglassey at gmail.com>:
>
>> The other idea is for ~/.sword to be created with soft links to
>> modules in /usr/share/sword and /usr/local/share/sword. Then a user
>> can 'delete' the module from there without having to go near apt. The
>> library will need to ignore the system directories and only see the
>> home dir plus any other custom dirs.
>>
> I don't like this idea because it alters the old behaviour. I have
> used both /usr/share/sword and ~/.sword and would hate if after
> updating the distro the modules would be messed up.

We'd have to make sure that old behaviour was maintained and worked as
expected after an upgrade.

I'd expect that modules would be installed with app module manager to
~/.sword and those would be the real files. They would be preferred to
the soft linked system modules.

I mean that the order of preference is:
~/.sword
then /usr/local/share/sword
then /usr/share/sword

I'm not sure where custom module paths would fit in. I'd guess using
the current system either below or above ~/.sword.

So the proposed new linking system would only link in files that don't
already exist in ~/.sword

Does that make sense? Is that roughly how it currently is?

Regards,
Daniel