From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Michael Bergandi <mbergandi@gmail.com>
Cc: eCos Developer List <ecos-devel@ecos.sourceware.org>
Subject: Re: Package versioning requirements for an epk
Date: Tue, 04 Jan 2011 14:35:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1101041617010.29104@sg-desktop.belvok.com> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2011-01-04 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 20:30 Michael Bergandi
2011-01-04 8:33 ` John Dallaway
2011-01-04 19:22 ` Michael Bergandi
2011-01-04 14:35 ` Sergei Gavrikov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1101041617010.29104@sg-desktop.belvok.com \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=mbergandi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).