On Thu, 16 May 2002, Uwe Brauer said:
3. Version numbers: couldn't the package numbers coincide with
the
version numbers of the maintainer? vm now does :), but auctex and
others do not. Yes pressing I will give this information, but
anyhow the convenience would be greater if the numbers coincided.
This is not always possible. The package number in XEmacs must always be
a valid number: this means that it cannot represent upstream versions
like 4.3.22 or 4.3a or 4.3p6 properly. Worse, since it always has to be
a number, if we ever had to upload a package at a time not synched to an
upstream release, we'd break hard:
upstream xemacs
4.2 4.2
4.3 4.3
4.4 (xemacs package change)
4.4 4.5 (whoops, out of synch)
I hear there's a new package system a-brewing that will allow more
flexibility in version numbers, but I don't know how far along in
development this is.
4. May be that has been asked already, but are there plans to write
a
tool, which allows to convert an already compiled package to to the
xemacs package standard?. I am thinking of something equivalent to
ALIEN for tgz2rpm.
(aside: I'd hope you don't need that for preview-latex :) If it's not
package-standard-compliant after `make install', tell me and I'll fix
it. It's meant to be.)
--
`There are not words enough to describe how fucked up imake is.'
--- Peter da Silva