From: Michael Bergandi <mbergandi@gmail.com>
To: John Dallaway <john@dallaway.org.uk>
Cc: eCos Developer List <ecos-devel@ecos.sourceware.org>
Subject: Re: Package versioning requirements for an epk
Date: Tue, 04 Jan 2011 19:22:00 -0000 [thread overview]
Message-ID: <AANLkTinrouO=LEuggvmtRuf8MG5grsiAQrMxcb7MdYCT@mail.gmail.com> (raw)
In-Reply-To: <4D22DB6A.7000605@dallaway.org.uk>
John,
> 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.
Well, it only works if you know how to tar the package properly! ;)
I used "tar czvf dummy.epk . ", when I should have used "tar czvf
dummy.epk * " from the root of my package directory. Once I figured
that out, it works fine.
Thanks for confirming it should work with 'current' as the version directory.
--
Mike
next prev parent reply other threads:[~2011-01-04 19:22 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 [this message]
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='AANLkTinrouO=LEuggvmtRuf8MG5grsiAQrMxcb7MdYCT@mail.gmail.com' \
--to=mbergandi@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).