From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16395 invoked by alias); 4 Jan 2011 14:35:22 -0000 Received: (qmail 16197 invoked by uid 22791); 4 Jan 2011 14:35:21 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST X-Spam-Check-By: sourceware.org Received: from mail-ew0-f49.google.com (HELO mail-ew0-f49.google.com) (209.85.215.49) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 04 Jan 2011 14:35:17 +0000 Received: by ewy20 with SMTP id 20so6069831ewy.36 for ; Tue, 04 Jan 2011 06:35:15 -0800 (PST) Received: by 10.213.10.12 with SMTP id n12mr334897ebn.66.1294151713726; Tue, 04 Jan 2011 06:35:13 -0800 (PST) Received: from sg-desktop.belvok.com ([86.57.137.251]) by mx.google.com with ESMTPS id q58sm15713557eeh.15.2011.01.04.06.35.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 04 Jan 2011 06:35:12 -0800 (PST) Date: Tue, 04 Jan 2011 14:35:00 -0000 From: Sergei Gavrikov To: Michael Bergandi cc: eCos Developer List Subject: Re: Package versioning requirements for an epk In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2011-01/txt/msg00002.txt.bz2 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