jed: slsh load path settings

[Rafael Laboissiere]

* G. Milde <g.milde at web.de> [2006-05-17 09:56]:

> On 16.05.06, Jörg Sommer wrote:
> > We can set a conflict on libslang2 (<< 2.0.6)
> 
> I just tried this, but I did not find any dependency on libslang2 in
> the control file. (Just a build deb on libslang2-dev.)

The dependency on libslang2 is automatically computed by dh_shlibdeps and
put into debian/substvars, which is later used to replace the
${shlibs:Depends} string in debian/control.  What I do not understand is why
I get in the Depends field  this:

    libslang2 (>= 2.0.1-1)

while I have version 2.0.6-2 installed in my chroot unstable system.
I am investigating this now.

> However, people using a mixed (stable)/testing/unstable/experimental
> environment will profit from this versionned dependency. Especially if
> they are only updating to unstable/experimental when required (like me).
> 
> So I still think the versionned dependency can save us some bug reports
> and some users much hazzle --- at a low cost.

Agreed.  However, the dependency on 2.0.6-2 should be automatically
generated as I commented above.  Otherwise, we could explicitly add
libslang2 (>> 2.0.6) to the Depends field of debian/control, in which case
Lintian would issue the following annoying warning:

W: jed: package-has-a-duplicate-relation depends: libslang2 (>= 2.0.1-1), libslang2 (>> 2.0.6)

We could also set a conflict on libslang2 (<< 2.0.6) as suggest by Jörg but
I have to think more about it.
 
-- 
Rafael