Re: [comp.emacs.xemacs] AUCTeX 11.84 released
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
Mats Lidell writes:
> If you can't download the build structure today, except through CVS,
> that is a problem then.
I disagree. The build structure is the source for the build
structure, and we don't distribute a binary for that. The binary
packages contain their own source, complete with all the files needed
to build the binary we distribute.
Just in a different arrangement (isn't everything just an arrangement
of 0 and 1?), one that is not the preferred form for modification as
an ongoing development process. I have in the past tackled problems
sometimes by patching binary libraries and executables (replacing a
wrong way to tackle a problem with a correct one is usually possible
in the same space if the correct solution is done with hand-coded
assembly language). Now that does not make the binaries source code
and "the preferred form for modification", even though, at a
customer's site, I'd rather patch the binary as a downstream
co-sufferer.
But in my opinion reducing the question of "preferred form for
modification" to what constitutes a convenient form for patching at
the receiving end is not the right question to answer with regard to
the spirit of the GPL.
> For each SUMO release there should be a source tar ball as well
I
> think.
Assuming that the binary tarballs do not qualify as source, that's
not good enough. The sources must be provided for *each* binary
distribution. As you know, the SUMOs lag the individual binary
packages by some months, and that SUMO source would rapidly become
outdated.
If the individual packages are updated on the package servers in
between Sumo releases, yes, something like that might be required on
the package servers. Whether it is a complete Sumo update or an
update of some corresponding source package or putting the respective
stuff inside of the package: if I had the possibility to download the
xemacs-base package from some package mirror on Christmas eve 2006,
there must have been something downloadable at the same date that
gives me the ability to create a derivative work of the downloadable
package at Easter 2007 in some build environment.
> Some words on the same location issue from the GPL FAQ. I
quote:
>
> "Can I put the binaries on my Internet server and put the source on a
> different Internet site?
>
> The GPL says you must offer access to copy the source code "from
> the same place"; that is, next to the binaries. However, if you
> make arrangements with another site to keep the necessary source
> code available, and put a link or cross-reference to the source
> code next to the binaries, we think that qualifies as "from the
> same place"."
Thank you for that reference. That wording clearly sanctions our
current practice. (I have to wonder if a lawyer reviewed it,
though.)
There are links and cross references to the source code next to the
package binaries? Since when? Anyway, how do you link an ftp- or
http server to a CVS server? In particular in a way facilitating
development (not just browsing)? I think that this FAQ entry rather
refers to the practice of offering source and binary package archives,
and some servers mirroring only the binaries and providing links for
the source.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta