>> We are fast approaching a feature freeze. I think >> I'll set it at >> September 15 at this point; that will leave a few weeks to >> debug anything >> major prior to the 3.5.12 release, which will most likely >> coincide with >> the release of Ubuntu Maverick. Any debugging >> information you can give me >> in the meantime would be great; I would very much like >> 3.5.12 to build >> properly under a non-Debian distribution. > > If we get that far, I think we'll have to provide a snapshot of the > official 3.5.12 source tarballs. As I mentioned, Slackers tend to be DIY > folks and many who might want to try 3.5.12 will want to build their own > packages rather than download binary packages. Here is an example of what > many Slackers will expect to find: > > http://slackware.mirrors.tds.net/pub/slackware/slackware-12.2/source/kde/src/ > > Just a directory of tarballs. > > Initially many will not be interested in the third-party apps. Only after > they prove to themselves they can build and use 3.5.12 will they look into > the third-party apps. Yet once again, they will want to find a source > tarball of some kind and not svn. > > There will be some Slackers who will want to download binary packages. You > have offered to provide those packages but currently, I amusing 12.2. Many > Slackers are using 13.0, 13.1, and Current. If all goes well I'll be able > to test building packages in those releases, but if you provide packages, > you'll have to support 12.2, 13.0, and 13.1. YOu can support Current, but > nobody will be upset if you do not. > > I realize lots has to happen between now and then. I'm just letting you > know ahead of time. > Works for me. I can generate tarballs of each module just as easily I can generate the monolithic one. Tim