[Pkg-blender-maintainers] Bug#463162: Bug#463162: scripts installed in the wrong directory

[Cyril Brulebois]

On 29/01/2008, Alex Romosan wrote:
> shouldn't that be ~/.blender/scripts/bpymodules ->
> /usr/share/blender/scripts/blender/bpymodules/
> 
> any reason why the data is installed in
> 
>   /usr/share/blender/scripts/blender/ 
> 
> instead of just
> 
>   /usr/share/blender/scripts/
> 
> do you expect non-blender scripts to go in
> /usr/share/blender/scripts/? 

Yes, there is a reason. The idea is to be able to ship blender scripts
in other packages, so that they are autodetected when blender is
launched. To do so, /usr/share/blender/scripts is scanned and for each
item there, a symlink is created from ~/.blender/scripts.

Examples: sunflow (the script isn't shipped yet, but such an upload is
ready), luxrender (being prepared, waiting for upstream to release its
first version).

I've described this mechanism in the “[ User-visible changes ]” section
of the 2.45-2 changelog, so that the maintainers of such packages know
how to ship blender scripts.


Getting back to your first question:

I could also special-case bpymodules (that is, creating an additional
link from scripts/bpymodules to /u/s/b/scripts/blender/bpymodules), but
I'd rather have bpymodules right under scripts/ so that no other package
can ship such a directory (dpkg would complain about files belonging to
two packages at the same time), preventing from running into cornercases
where the final symlink would depend on the order in which the items
under scripts/* are scanned, or similar.


I'm planning to move bpymodules one level up as I described, but I'm of
course willing to hear any other suggestion.

Cheers,

-- 
Cyril Brulebois
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-blender-maintainers/attachments/20080130/bf5ccd91/attachment-0001.pgp