On Wednesday 26 March 2008, Alexander Wagner wrote: > Hi! > > >>> If you're at the bleeding edge, you'll have to package the > >>> styles and stuff with scid (which I consider a major design > >>> fault) plus people will most likely not know how to use > > [...] > > >>> enable it would probably be good, or the config file you > >>> mentioned. (Though this will involve some work.) > > > > I second that. > > > > I am trying to get the maintainership of some debian > > packages (Scid which is still on 3.6.1, Skak, Chess12). > > So I can update them to the last versions. > > 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.. But one issue that arise is the name of the package. The old Scid is dead, Chessdb exists (existed) 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 ;)) > > > But Debian is still one of few distributions which include > > them (Suse dont include them. although version 10.3). > > Chessfss is not included in Debian. > > 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. But other distro's have their own dependencies. > > > 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. > > > And see if skak can be enabled (optional?) in the future > > versions... > > Probably there is a way to do it in a modular manner. There > could be a "failsafe default", something that uses the old > chess package, but is still clean LaTeX2e and maybe a > "modern setup" that uses things like skak et al. Some, "if > you know how to set it up, we need <documented her in detail>, > this will give you the perfect output" switch. > > 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. > > 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.. gr. Willem -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ------------------------------------------------------------------------- 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
