No registered users in community xowiki
in last 10 minutes
in last 10 minutes
[Xotcl] Re: [Xotcl] Re: [Xotcl] Using source with the xodoc tool / Debian
From: <uwe.zdun_at_uni-essen.de>
Date: Tue, 19 Dec 2000 18:12:36 +0100 (CET)
>>>>> "KL" == Kristoffer Lawson <setok_at_fishpool.com> writes:
KL> On Tue, 19 Dec 2000 uwe.zdun_at_uni-essen.de wrote:
>> we could also merge components that are split across files into one
>> documentation file. I'm not sure which solution is the best one ...
>> what do you think?
KL> I think the best behaviour would be a combination of the two given
KL> possibilities:
KL> Each code file does get its own documentation file, but there is one
KL> package documentation file that lists which files are part of the
KL> packages. This document file would then link to the per-file document
KL> files.
yeah, that sounds sensible. I take a look at how we can realize this
behavior conveniently ...
KL> On another issue we have made Debian packages of XOTcl (0.82, but 0.83 is
KL> on the way) if someone is interested.. They're not extensively tested but
KL> they seem to work on the machines here. Probably candidates for merging
KL> into the official Debian system at some later time.
>>
>> great! if you like to maintain Debian packages & have a web page for
>> them, we can link this page with the XOTcl download page?
KL> Yeah, we should still test them on a clean machine and if that works
KL> then we can stick them up somewhere. I'll get back to you once we've
KL> done that. There shouldn't be any major problems anyway. I just
KL> did a "dpkg -i" for the 0.83 package and except for a minor issue with
KL> pkgIndex.tcl it seems to be working.
ok. just drop us a note, when you're through with it
--Uwe
Date: Tue, 19 Dec 2000 18:12:36 +0100 (CET)
>>>>> "KL" == Kristoffer Lawson <setok_at_fishpool.com> writes:
KL> On Tue, 19 Dec 2000 uwe.zdun_at_uni-essen.de wrote:
>> we could also merge components that are split across files into one
>> documentation file. I'm not sure which solution is the best one ...
>> what do you think?
KL> I think the best behaviour would be a combination of the two given
KL> possibilities:
KL> Each code file does get its own documentation file, but there is one
KL> package documentation file that lists which files are part of the
KL> packages. This document file would then link to the per-file document
KL> files.
yeah, that sounds sensible. I take a look at how we can realize this
behavior conveniently ...
KL> On another issue we have made Debian packages of XOTcl (0.82, but 0.83 is
KL> on the way) if someone is interested.. They're not extensively tested but
KL> they seem to work on the machines here. Probably candidates for merging
KL> into the official Debian system at some later time.
>>
>> great! if you like to maintain Debian packages & have a web page for
>> them, we can link this page with the XOTcl download page?
KL> Yeah, we should still test them on a clean machine and if that works
KL> then we can stick them up somewhere. I'll get back to you once we've
KL> done that. There shouldn't be any major problems anyway. I just
KL> did a "dpkg -i" for the 0.83 package and except for a minor issue with
KL> pkgIndex.tcl it seems to be working.
ok. just drop us a note, when you're through with it
--Uwe
-- Uwe Zdun Specification of Software Systems, University of Essen Phone: +49 201 81 00 332, Fax: +49 201 81 00 398 zdun_at_xotcl.org, uwe.zdun_at_uni-essen.de