public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
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 08:33:00 -0000	[thread overview]
Message-ID: <4D22DB6A.7000605@dallaway.org.uk> (raw)
In-Reply-To: <AANLkTinfh4QZCuPTYN8=X7Z1YCaob+6nn5r8_kgrBY4c@mail.gmail.com>

Hi Michael

Michael Bergandi wrote:

> Can someone explain/confirm the versioning requirements for an epk
> package distribution?
> 
> 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.

Using "current" as a version directory within a .epk file should work,
but the tool is intended for easy distribution of package _releases_ so
version directory names in the "v1_0" style make more sense in the
majority of cases.

For avoidance of doubt, the directory path fragments in ecos.db should
always point to the parent directory of the package version directory.

John Dallaway
eCos maintainer

  reply	other threads:[~2011-01-04  8:33 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 [this message]
2011-01-04 19:22   ` Michael Bergandi
2011-01-04 14:35 ` Sergei Gavrikov

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=4D22DB6A.7000605@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --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).