[Scrollkeeper-devel] Re: relocatable package support

[Dan M. <d-...@uc...>]

On Wed, 27 Jun 2001, Laszlo Kovacs wrote:

> First, I think we should rename the scrollkeeper-update-identifier
> script to scrollkeeper-update-url.

Good point. We are only updating the one attribute of the element.

> There would be one more needed:
> 
> 4. Update the url in a set of OMF files in the same subdirectory
> structure with urls from docs specified by a directory only. Both the
> base filename (2) and the relative filename (3) should work in this
> case.

This would be the preferred way to do things.

> The user should be able to do something like this:
> 
> scrollkeeper-update-url $prefix/share/omf/scrollkeeper
> $prefix/doc/scrollkeeper
> 
> and this should do everything they need.

:) 

> This can become quite complicated to be used together with
> scrollkeeper-preinstall, it will need a good documentation.

Hmm...  I think it would be helpful to figure out a little more about what
information we have access to for passing to the post-install script.  We
can either have the OMF file originally contain the full non-relocated
path.  Or, it could have the part of the path without $prefix and then
sk-update-url could just add the prefix.  Or, ...

I think the best solution would require that the post-install script have
access to the unrelocated and relocated prefixes.  Then we would do
everything exactly as we did before and if somebody wants to make it
relocatable they just add a post-install script which basically just does
a search and replace on the prefix strings.  

So, does anybody know whether we will have access to both of the prefixes
(before and after) in the packaging systems we care about?

Dan