- Therion - speleo.sk

[therion-users] Debianizing therion
by Wookey 20 Nov '02

20 Nov '02

I've started packaging therion and am begining to understand how it goes together. I have a fundamental question to ask before I do much more: Do the upstream authors (that Stacho and Martin) want this to be a native debian package or not? In a normal package there is the tarball I get from upstream, then there is a set of debian patches that are applied to it to make it fit the debian path and rules and add a debian 'control' file (really a makefile) that makes sure the package can be built in the right way so it will work on autobuilders. In a native debian package there is no patch to make these changes - the control files are in the normal tarball. Survex is done this way. It is entirely up to you guys which way we do this. A native package is simpler and is slightly less work overall, but it does move some responsibility for making the build-process work right from me to you, and you may not want to do that, or not yet. In practice it mostly means adding a /debian dir that I supply, and maybe some build-process changes if necessary. Tell me what you think. In a week or so I expect I'll send you the first version to look at. Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/

2 2

[therion-users] Update
by Stacho Mudrak 13 Nov '02

13 Nov '02

I've updated source code - some bugs are fixed, experimental symbols for block and debris walls - with randomness, handmade look ;-) S.

1 0

[therion-users] ;-)
by Stacho Mudrak 11 Nov '02

11 Nov '02

Uff, last mail spent 6 days on the way... Please ignore it. S.

1 0

[therion-users] Re: New version
by Stacho Mudrak 07 Nov '02

07 Nov '02

> Hi people, I've just joined up. I downloaded and compiled this OK on a > debian woody box. I've got some small changes for you for the README and > INSTALL docs as a result, which I'll mail as soon as I get the network card > n my laptop working. The current build process assumes you have bin/therion > on your PATH when you do make xtherion. I assume this needs to be the > current version of therion, not just any old version. This is likely to > cause trouble, as normally the ~home/therion/bin isn't going to be on the > path but /usr/local/bin/therion will be and that'll be the old version. > Will that break? Of course, you're right ;-) The build process is now done a very dirty way and I'm very interested in, to make it GNU compatible (automake etc...), but we've a lot of other things on TODO list, that are too hot... If you're interested in, I can send you the map of our real (2 km) test cave (cca500kB in PDF, 40kB in therion format - if you're able to run therion - it would be a very nice test), that you will see, how the map of real cave processed by therion looks like. We can not put it on the web, as a motivation for other people, because it's very "sensitive" cave - in fact we have forbidden access to it (by ministry of environment) and we would have big problems, if some officer would know, that we're still doing explorations there... And we've no other cave maps, because until now we put 95% of our effort into programming. Now it's slightly changing, when we're able to put into maps all we need, we will probably be more editing maps than programming. In the very near future, we need to add to maps some basic things, that are still missing like graphical scale, north arrow, surveyors and dates and than generate automatically the map legeng - from the symbols that were used in a map. Then 2D output should be more or less finished (ha - it seems I'm still optimistic). But we urgently need some 3D passage model. It'll be a part of xtherion, because I've found one very nice parser of OpenGL into Tcl/Tk. Our goal is to minimize entering up-down-left-right data, but using map plan, extended profile and given sections (all parts of 2D input) generate a 3D passage wall model. I'm very keen on testing such an algorithms, because I've never seen something like this and I believe, it would save our time and improve the 3D model. Of course in parallel, we're planing to write some therion cookbook. README file now serves more like a reference guide, because sometimes I forget, how I've programmed something. That's all about the current state of therion project. Any help or comments are welcome. S. P.S. I'll change right now the Makefiles in a way, that only newly compiled therion will be used in xtherion compilation. I've been using symbolic links from /usr/bin, that pointed to therion, so I didn't recognize such a problems. P.S.2. Something went wrong with the setup of mailing list, so if you got this message twice, I'm sorry.

3 2

[therion-users] New version on the Web
by Stacho Mudrak 06 Nov '02

06 Nov '02

I've updated downloadable files. I've recognized that binary releases contain old tex and matapost macros. Also makefiles were slightly modified. S.

1 0

[therion-users] New version
by Stacho Mudrak 06 Nov '02

06 Nov '02

I've fixed some serious bugs on weekend, the new version of therion is on the web. S.

2 2

[therion-users] Update
by Stacho Mudrak 14 Oct '02

14 Oct '02

During the weekend, I've fixed several bugs. New version is on the web. Regards, S.

1 0

[therion-users] It works!
by Martin Sluka 12 Oct '02

12 Oct '02

Hello --

1 0

[therion-users] Mailing list
by Stacho Mudrak 11 Oct '02

11 Oct '02

Hello everybody, I would just like to let you know, that we've changed therion mailing list. You were moved to the new list automatically, so you do not need to subscribe again. Regards, S.

1 0

[therion-users] Skuska...
by Stacho Mudrak 11 Oct '02

11 Oct '02

Funguje to voobec???

1 0