I have made the 0.4.1~pre20061221 debian packaging of the latest
snapshot. This includes the wiki docs and the current source and debs
are available at:
http://wookware.org/files/therion/
However I have a problem with the packaging.
Debian packages normally include the original source tarball plus a
debian diff for the changes. However the changes now include all the
wiki html and images. The images are not representable in a diff so it
doesn't work. The above package has been done without an upstream
tarball for the source.
I am not sure what to do about this. I see these options:
1) uuencode all the images
Pro: farily simple - packagin needs to uudecode them all before
normal packaging - no other changes.
Cons: Makes source 35% bigger - not totally crazy but still 1Mb extra.
Makes packaging more fiddly due to need to convert to/from uuencode
whenever there is a wiki export update
2) Make therion a debian native package
Pro: can then just use standard mechanisms
No wasted space or extra faff
Con: therion isn't a debian native package, and it means I can't do a
debian update without there being abump in the therion version. This
has caused problems with survex so I'm not too keen.
This is effectively what has been done with the debs I've currently
built.
3) Include wiki export in upstream tarball
Pro: Makes things trivial from my POV
Con: You may not want to do this as you already have the wiki - do
you want docs in source as well?
Makes source much bigger: dump is ~3.5MB
4) Split therion source docs and code upstream
Pro: has the same effect as 3, but code download is still small.
Con: You need to do a bit of work to move thbook sources into docs
tarball
So, the question for therion authors/admins (who shouldn't really have to
worry about debian packaging), is do you think including the wiki docs
in either the main source tarball or a different docs one (and move
the thbook into that too) is a good idea or not?
If you do then I suggest this is the best way to go. If not I will
probably go the uuencode route for now, unless/until someone has a better
idea.
Sorry to bother you with this - I had never realised that debian diffs
cannot introduce binary files not in upstream - it's a bit cack really
in a situation like this.
Wookey
--
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/ play: http://wookware.org/
On 2006-12-19 12:20 +0100, Norbert Preining wrote:
> Hi!
>
> On Die, 19 Dez 2006, Norbert Preining wrote:
> > > Although for the purposes of texlive compatibility I think the
> > > existing 0.3.10 in debian testing will be just as good.
> >
> > Ok, can take a look at this, too.
>
> Hmm, it is quite hard to check for dependencies in the source c++ code.
> I have another idea: Can you send me some typical file which should be
> compiled with metapost and pdflatex (or whatever)?
There is a set of files for a large project here:
http://wookware.org/mulu/mulu.tgz
common_layout.th has some metapost code in it. The .th2 files are the
ones that describe the lines and symbols use to draw each section. the
thconfig file sets which files and styles are used for each dir (try
benarat/terikan/ as a reasonably complex and complete example).
As I said I'm not sure this is really going to help that much as it is
too far removed from Tex to be relevant.
I think the tex, mpost and (maybe) texenc dirs in the source are the
bit that show what tex and metapost functions are used.
> I have seen comments on metafun, too, do you use context?
I don't understand this question. Martin, Stacho?
> As I said, the best option is to send me some medium complicated files
> which should be do-able with the dependencies, and I will check them.
> Thank
Well that Mulu.tbz tarball is an example. Unpack it. and apt-get install therion.
Then
cd benarat/terikan
therion
and watch it process. (You can do therion at the top level but that
could take a while).
I suppose I could try the same thing with texlive and see what
happens. But right now I need to produce some output for an expedition
leaving just after xmas. I'll try Texlive once that panic is over.
Wookey
--
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/ play: http://wookware.org/
