Re: GNOME category exists now?
Christopher Faylor wrote: This is the list of sections that I found in ftp://ftp.gnu.org/debian/dists/sid/main/binary-i386/Packages.gz : admin electroni interpret misc perl tex base embedded kde net pythontext comm games libdevel news science utils devel gnome libs oldlibs shellsweb doc graphics mail otherosfs sound x11 editors hamradio math The package list found there is not a one-to-one with the web page that you referenced but gnome is listed in the definitive list, so it's ok to use it in Cygwin, too. Besides this, how about the spelling, is it ok to use capitals like i.e. GNOME? Gerrit -- =^..^=
Re: GNOME category exists now?
Christopher Faylor writes: We don't do things exactly like Debian in every case but if there is precedent in Debian it helps to make the Cygwin decision. Except maybe in this specific case, if you know that Debian sections are considered foo http://lists.debian.org/debian-devel/2003/04/msg00159.html Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: update: guile-1.6.5 and 1.7.1.CVS
Gerrit P. Haase writes: Sorry, missed this one. Thanks. I didn't think of that. If any problems, please remove 1.6.4-12, it is buggy and 1.6.5 should be better on all accounts. And keep 1.6.4-2? 1.6.4-2 is for the cygwin1.3 abi, I think it's safe to remove that now. Please just keep 1.6.5-1 and 1.7.1.20041006-1. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: Missing DocBook XML DTD
Jani Tiainen wrote: Actually in my installation I have no /usr/share/xml/docbook-4.1.2, instead I have usr/share docbook-xml42, and under /usr/share/xml is _only_ libglade subdir... Wondered that while looking those one of scripts... Are packages installed improperly in wrong directory? Hmmm, the cygwin docbook packages are there because the maintainer decided to put them there. Make symlinks or mount the according paths or change the script to your needs. You may also start a discussion with the docbook-x* maintainer to use paths like recommended by the FHS: http://www.pathname.com/fhs/pub/fhs-2.3.html#USRSHARESGMLSGMLANDXMLDATA or like debian or fedora or whatever you think is better. Gerrit -- =^..^=
Bash updates, bashdb, bash_completion, etc.
Hello all, Let me just start by saying that I really think bashdb would be a nice addition to Cygwin. That said, I'll need some convincing to add it to mainline Bash as I don't want to maintain YA out-of-tree patch for Bash if I can help it. As for Bash-2.05b-17: I've applied Pierre's patch to bash-2.05b-16 and am compiling it now (I've got a coffee break I can use for that). As for Bash-3: it doesn't currently get through the tests and I do not have the time at the moment to figure out why not. The reason for this is very simple: I don't have a Windows machine at home so all I have for testing is my lunch and coffee breaks. (This same lack of a Windows machine had a rather dramatic impact on the time I had allocated for the Cygwin project a while ago, when I was at home for nearly four consecutive months.. donations are welcome ;) Reini, if you still intend to package bashdb and bash_completion, I'll be happy to work with you to integrate them into the bash package. However, as you have already stated that you don't want to maintain bash and I have already stated that I don't want to maintain bashdb or bash_completion, we'll have to find some solution to this or accept a stalemate. Please feel free to mail me privately about this. rlc PS: I've subscribed this (hotmail) address to cygwin-apps as I don't have E-mail at home either and the Gmane equivalent of this list doesn't allow posting. There's no need to copy to [EMAIL PROTECTED] or to this address.. _ Powerful Parental Controls Let your child discover the best the Internet has to offer. http://join.msn.com/?pgmarket=en-capage=byoa/premxAPID=1994DI=1034SU=http://hotmail.com/encaHL=Market_MSNIS_Taglines Start enjoying all the benefits of MSN® Premium right now and get the first two months FREE*.
Please add me to cvsadmin group on sources
I want to be able to fix up keyword expansion modes, and toggle states of revisions (for move-simulation). There is nothing that can be done with cvsadmin that cannot be done by editing the RCS files directly - cvs admin is just a bit more convenient and safer. Max.
setup.exe - RFC: reorganizing source into category directories
Setup.exe has a *lot* of source files. To make the source a little more comprehendable, I'm planning on moving certain subsystems which effectively are utility libraries in their own right into subdirectories. This should hopefully be a step on the path to untangling the logic and the GUI code. To begin with, I'm proposing the following new directories: One for all source imported with little or no modification from external sources - that is md5.* (from libmd5-rfc sourceforge project) and rfc1738.* (from squid). A possible name for this would be srclib. One for NetIO and io_stream class heirarchies, and geturl.* (associated helper functions). This is a large (116KB) chunk of code, exclusively concerned with IO. A possible name for this would be cygsuio. One for all image files (icon, bitmaps). Name images. Comments welcome, especially if anyone has any preferences for different names. Max.
Re: setup.exe - RFC: reorganizing source into category directories
On Thu, 28 Oct 2004, Max Bowsher wrote: Setup.exe has a *lot* of source files. To make the source a little more comprehendable, I'm planning on moving certain subsystems which effectively are utility libraries in their own right into subdirectories. This should hopefully be a step on the path to untangling the logic and the GUI code. To begin with, I'm proposing the following new directories: One for all source imported with little or no modification from external sources - that is md5.* (from libmd5-rfc sourceforge project) and rfc1738.* (from squid). A possible name for this would be srclib. I assume you plan to build those into a library and link with it later? How about naming the directory after the library (e.g., librfc or something)? One for NetIO and io_stream class heirarchies, and geturl.* (associated helper functions). This is a large (116KB) chunk of code, exclusively concerned with IO. A possible name for this would be cygsuio. Again, libio? One for all image files (icon, bitmaps). Name images. Would it make sense to move res.rc and resource.h in there as well and call the directory resources or libresource? Comments welcome, especially if anyone has any preferences for different names. Max. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
Re: setup.exe - RFC: reorganizing source into category directories
Igor Pechtchanski wrote: On Thu, 28 Oct 2004, Max Bowsher wrote: Setup.exe has a *lot* of source files. To make the source a little more comprehendable, I'm planning on moving certain subsystems which effectively are utility libraries in their own right into subdirectories. This should hopefully be a step on the path to untangling the logic and the GUI code. To begin with, I'm proposing the following new directories: One for all source imported with little or no modification from external sources - that is md5.* (from libmd5-rfc sourceforge project) and rfc1738.* (from squid). A possible name for this would be srclib. I assume you plan to build those into a library and link with it later? How about naming the directory after the library (e.g., librfc or something)? No. I don't think it's worth it - there is only one object for the md5 code, and one object for the rfc1738 code. Despite the incidental presence of rfc in both of the names, they are entirely unrelated, so I don't think it would be correct to bundle them together. One for NetIO and io_stream class heirarchies, and geturl.* (associated helper functions). This is a large (116KB) chunk of code, exclusively concerned with IO. A possible name for this would be cygsuio. Again, libio? A rather too-generic name for some rather specific code, IMO. This one would make sense as a library eventually, once I've picked out all the usages of global variables from the main setup code. One for all image files (icon, bitmaps). Name images. Would it make sense to move res.rc and resource.h in there as well and call the directory resources or libresource? I like that idea - I'd pick the name resources. Max.
RE: setup.exe - RFC: reorganizing source into category directories
Setup.exe has a *lot* of source files. To make the source a little more comprehendable, I'm planning on moving certain subsystems which effectively are utility libraries in their own right into subdirectories. This should hopefully be a step on the path to untangling the logic and the GUI code. Hear hear. I also think Igor's resources dir is a good idea. -- Gary R. Van Sickle
