xemacs-package for VM 8.0.8

[Steve Youngs]

* Robert Widhopf-Fenk <hack at robf.de> writes:

  > On Monday, February 18, 2008 at 08:03:04, Stephen Turnbull, XEmacs 21 4 Release Manager wrote:
  > [...]
  >> Robert, I assume that you want to keep the VM version number in sync
  >> with its XEmacs package version, as Kyle did.  However, XEmacs package
  >> versions are not compatible with double-dot versions, AFAIK.  Please
  >> consult with Norbert and maybe Steve Y and Ville about that.

  > Hi Norbert,

  > how should I assign the version number of the package so it
  > matches to the upstream version

Take my advice... don't.  Sooner or later they _will_ get out of sync so
there's no point in trying.  You can always get to the upstream version
via #'package-get-info anyway...

,----[ C-h f package-get-info RET ]
| `package-get-info' is an interactive autoloaded Lisp function
|   -- autoloads from "package-get"
| 
| Documentation:
| Get information about a package.
| 
| Quite similar to `package-get-info-prop', but can retrieve a lot more
| information.
| 
| Argument PACKAGE is the name of an XEmacs package (a symbol).  It must
| be a valid package, ie, a member of `package-get-base'.
| 
| Argument INFORMATION is a symbol that can be any one of:
| 
|    standards-version     Package system version (not used).
|    version               Version of the XEmacs package.
|    author-version        The upstream version of the package.
|    date                  The date the package was last modified.
|    build-date            The date the package was last built.
|    maintainer            The maintainer of the package.
|    distribution          Will always be "xemacs" (not used).
|    priority              "low", "medium", or "high" (not used).
|    category              Either "standard", "mule", or "unsupported"..
|    dump                  Is the package dumped (not used).
|    description           A description of the package.
|    filename              The filename of the binary tarball of the package.
|    md5sum                The md5sum of filename.
|    size                  The size in bytes of filename.
|    provides              A list of symbols that this package provides.
|    requires              A list of packages that this package requires.
|    type                  Can be either "regular" or "single-file".
| 
| If optional argument ARG is non-nil insert INFORMATION into current
| buffer at point.  This is very useful for doing things like inserting
| a maintainer's email address into a mail buffer.
| 
| If optional argument REMOTE is non-nil use a package list from a
| remote site.  For this to work `package-get-remote' must be non-nil.
| 
| If this function is called interactively it will display INFORMATION
| in the minibuffer.
| 
| Invoked with:
| 
| M-x package-get-info
`----

(package-get-info 'vm 'author-version)
 => "7.19"

(package-get-info 'vm 'version)
 => "7.26"

  > I so not see any rules for the other packages and was thinking about

  >   MAJOR.MINOR.PATCH

  > to transform by

  >   "%d.%2d%d", MAJOR, MINOR, PATCH

  > e.g. for 8.0.8 the package version 8.008, for 8.1.2 the
  > package version 8.012 or are there any rules or limitation
  > for the package numbers?

That wouldn't work for #'pui-list-packages.  The version columns are
formatted to n.nn, so 8.008 would transform to 8.00 in PUI's buffer.


-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|       SXEmacs - The only _______ you'll ever need.       |
|         Fill in the blank, yes, it's THAT good!          |
|------------------------------------<steve at sxemacs.org>---|
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 316 bytes
Desc: not available
Url : http://calypso.tux.org/pipermail/xemacs-beta/attachments/20080223/2ba130f9/attachment.bin