On Wed, 03 Sep 2014, Guillem Jover wrote:
> Hmm, this was supposed to be fixed with the upload that made the check
> coherent with the implementation, this is what the man page says for
> the symlink to directory switch (which is what lilypond-doc is using):

[...]

> or is there something else I missed on the update (perhaps the omitted
> stuff referenced by [1]?).

Sorry; 1: was supposed to indicate that I hadn't checked the your VCS
repository. And now that I see, I was reading the manpage from 1.17.10
instead of 1.17.13 because I stupidly assumed that
dpkg-maintscript-helper was in dpkg-dev, not dpkg... My bad.

The documentation in 1.17.13 is clear enough now that I'm actually
reading that version. Sorry.
 
> Sure, it seems and it is a bit backwards, but that's because the
> initial implementation could only handle absolute symlink targets for
> dir_to_symlink, so “it seemed to make more sense” to have both be
> symmetric. When the dir_to_symlink got fixed to also accept relative
> symlinks, I actually got a bit bothered by the new asymmetry, but…

Ah; makes sense. I think lilypond's symlink happened by the expedient of
just doing it instead of using dpkg-maintscript-helper.

> … neither me nor Helmut did think of this obvious solution, I don't
> know why!? maybe just because we had our minds elsehwere during the
> Bootstrap Sprint :), I'll try to recall if there was actually any
> problem. But otherwise, I'll just be adding relative symlink support
> to symlink_to_dir in dpkg 1.17.14, but be aware that previous dpkg
> version will either accept them but not perform the actual switch or
> outright refuse them.

Right; I'll fix the lilypond postinst. It's sort of embarrassing too,
because I thought I tested that it worked... but it's likely that I
wasn't paying enough attention (or had managed to remove the older
version).

-- 
Don Armstrong                      http://www.donarmstrong.com

Nearly all men can stand adversity, but if you really want to test his
character, give him power.
 -- Abraham Lincoln


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to