This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
Re: Package versioning requirements for an epk
- From: Sergei Gavrikov <sergei dot gavrikov at gmail dot com>
- To: Michael Bergandi <mbergandi at gmail dot com>
- Cc: eCos Developer List <ecos-devel at ecos dot sourceware dot org>
- Date: Tue, 4 Jan 2011 16:35:00 +0200 (EET)
- Subject: Re: Package versioning requirements for an epk
- References: <AANLkTinfh4QZCuPTYN8=X7Z1YCaob+6nn5r8_kgrBY4c@mail.gmail.com>
Hi Michael,
On Mon, 3 Jan 2011, Michael Bergandi wrote:
> Can someone explain/confirm the versioning requirements for an epk
> package distribution?
The gory details about eCos 'Package Versioning':
http://ecos.sourceware.org/docs-latest/cdl-guide/package.versions.html
> From what I can tell, you used to be able to get away with
> $PACKAGE/current, but it looks like ecosadmin.tcl might have been
> updated to force proper verisioning. The package I am testing does use
> 'current' as the version directory in the epk, but the ecosadmin.tcl
> tool is barking about the package not having a version directory.
In no way I could reproduce this.
Sergei