WilSoft schrieb:
Hi!
>> Thats good news, so you want to get the current 3.6.xx
>> line to Debian? (This is especially of interest as it
>> will also move on to the spin-off distributions.)
>
> I am building the package 3.6.22 for debian. But for now I
> dont have the formal debian-maintainer title so I have to
> work for that first..
Ic.
> But one issue that arise is the name of the package. The
> old Scid is dead, Chessdb exists (existed)
The tempus here is past tense, right?
> in de the debian distribution so we need to figure out an
> other name for Scid before it can be accepted as a
> package. (who wants to win the cake for the most original
> name ;))
Well, the sf-registration is just scid2. This is probably
not very original, but well...
>> Point here is, that Debian offers them by means of
>> TeXLive. If you install the "normal tex" you'll not get
>> it. Including TeXLive into debian was a major step and
>> the other distributions still just install the old tetex
>> package structure.
>
> Correct. We can make a suggested depencency (otherwise the
> whole Tex package is installed. Not everyone needs it) for
> debian.
Of course.
> But other distro's have their own dependencies.
Not only the other deps but also "no suitable package
available", I fear.
>> > So I would suggest, keep it on the current
>> > chess-package.
>>
>> That is keep out skak in your current implementation
>> entirely? (Just a question out of curiosity.)
>
> At least for 3.6.23. Chess12 is working fine now I think.
Agree here. I mean one could fix the obvious stuff like
\usepackge{a4} or whatever. (Did not check the code
recently.) Ulrichs pointer to the TUG document was a prettey
good one here.
>> But as you've to touch some code in there anyway you could
>> probably already prepare it for the move to another package.
>> I don't know the internals of scids TeX export, but probably
>> it could be desinged that way and this will probably even
>> safe work later on?
>
> I think thats not a big problem to solve.. As I can see
> the code is clean and it should be easily integrated (well
> .. I think it should). One thing crossed my mind. Does
> modifying the tex-code output interact with the HTML
> output? I havent digged into that one.
Good question. I'd guess Pascal has an anwer here as he did
quite an improvement on the HTML front.
>> BTW: if you want to work on this part, and your work is
>> greatly appreciated, there's a cvs set up at sourceforge
>> and you could surley get (writing) access to it.
>
> I surely will dive into it. But cant garanty you a
> timeline..
Well I can't give you an timeline for my stuff either ;)
Thats the "bad thing" with spare time projects. Hence I
can't promise you an entirey polished CC module or an
entirely polished Input Engine / DGT support for tomorrow as
well.
Anyway, I think that getting more people involved who are
working on different parts isn't a bad thing :)
--
Kind regards,
Alexander Wagner
Universitaetsbibliothek Ilmenau
Langewiesener Str. 37
98693 Ilmenau
Tel.: 03677/69-4521 , Fax.: 03677/69-4617
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Scid-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scid-users
