Re: [Strasheela-devel] strasheela-0.8.3
Status: Beta
Brought to you by:
t-anders
|
From: Torsten A. <tor...@gm...> - 2007-08-08 08:43:45
|
Dear Toni,
thank you very much for your packaging!! You are very quick indeed!
Your improvement to install-all.sh certainly makes sense. I will
update it and the similar scripts accordingly.
Concerning your question, both directories stem from code in
STRASHEELADIR/contributions/ and are part of Strasheela. I feel that
developers of contributions should be recognised, so their code goes
into different directories. More specifically, YOURLIBDIR/mozart/
cache/x-ozlib/authorname/* is the result of STRASHEELADIR/
contributions/ExtensionTemplate. This extension is there for
documentation purposes. For a clean package, you may safely leave out
its resulting *.ozf files. But please leave the resulting *.ozf files
of Kilian Sprotte in YOURLIBDIR/mozart/cache/x-ozlib/.
BTW: I noticed that you create different packages for strasheela and
strasheela-doc. Every extension in STRASHEELADIR/contributions/ comes
with its own documentation. There is usually a directory doc
containing HTML files (e.g., STRASHEELADIR/contributions/anders/
Pattern/doc). It is important that the relative folder structure of
STRASHEELADIR/doc and STRASHEELADIR/contributions/AUTHOR/CONTRIB/doc
are maintained, because their files link to each other. Moreover, a
few links point even to files which are not stored in any
documentation directory (e.g., to STRASHEELADIR/_ozrc or to the dir
STRASHEELADIR/contributions/ExtensionTemplate).
For these complications, I haven't provided separate documentation
releases. In order to automate a documentation release creation, some
script would have to go through the doc HTML code, search for local
links and include every local file linked... Perhaps you have a
better idea? An easy solution (risking a few broken links) would be a
script similar to install-all.sh: it
would just include STRASHEELADIR/doc and every STRASHEELADIR/
contributions/AUTHOR/CONTRIB/doc.
Thank you!
Best
Torsten
On Aug 7, 2007, at 10:15 PM, Toni wrote:
> Hi,
>
> I'm just playing around with strasheela to package it :)
>
> a small improvement to your install-all.sh:
> use 2 parameters, the first for an installation-prefix and the
> second for the
> installation directory.
> As I install strashella "globally"; I move the resulting files
> to /usr/lib/mozart (or /usr/lib64/mozart for 64bit) and to package
> them with
> rpm I need a buildroot-dir as prefix. See my attached version of
> the script.
>
> A qeustion according some oz files:
> %dir %{_libdir}/mozart/cache/x-ozlib/sprotte
> %{_libdir}/mozart/cache/x-ozlib/sprotte/*
> and
> %dir %{_libdir}/mozart/cache/x-ozlib/authorname
> %{_libdir}/mozart/cache/x-ozlib/authorname/*
>
> are these examples or do they belong to strasheela ?
>
> I guess I'll upload the new packages tomorrow on our server.
> http://packman.links2linux.de/package/strasheela
>
> have fun
> Toni
> <install-all.sh>
|