public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tod M. Neidt" <tod@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] CUnit - !!! Name error in CUnit-1.0-4: multiple version parts.
Date: 11 Mar 2002 16:33:19 -0600	[thread overview]
Message-ID: <1015886000.610.12.camel@silica.localmosci> (raw)
In-Reply-To: <3C8D26A2.6090505@colubris.com>

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

Hi!

The current Gentoo package naming convention can be found in

http://www.gentoo.org/doc/gentoo-howto.html

In this specific case I would suggest appending the patch number to the
version number with a "." instead of a "-" (should be kosher with
portage) and then use appropriate munging to transform the ebuild name
to the tarball name. I guess I would also pad the version number with a
extra 0 so that it is less likely to have a version collision with the
possibly release of the real version 1.0.4 in the future, i.e.
CUnit-1.0.0.4.ebuild

Since this is a small ebuild I have attached an example of how I would
approach it. The munging may be overkill, but it illustrates how to make
the ebuild version independent (at least within this 1.0 patch cycle) to
make maintenance easier. I have not tested this ebuild, it is intended
to be informative only. ( please test and submit a working verison to
bugs.gentoo.org) Note: the <command> || die syntax instead of try
<command>, see skel.ebuild.

If you have any additional questions, feel free to contact me.

Hope this helps,

tod





[-- Attachment #2: CUnit-1.0.0.4.ebuild --]
[-- Type: text/plain, Size: 694 bytes --]

# Copyright 2002 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License, v2 or later
# Author Yannick Koehler <ykoehler@hotmail.com> (mostly inspired by existing ebuild scripts)
# $Header$

patchversion=${PV##*.}
MYPV=${PV%.0*}
MYP=${PN}-${MYPV}-${patchversion}
S=${WORKDIR}/${MYP}
DESCRIPTION="CUnit 1.0-4 C Unit Test Framework"
SRC_URI="http://prdownloads.sourceforge.net/cunit/${MYP}.tar.gz"
HOMEPAGE="http://cunit.sourceforge.net"

DEPEND="virtual/glibc"

src_compile() {
	
	./configure || die "Configuration failed."
	
	emake || die "Parallel make failed."
}

src_install() {
	
	make install || die "Installation failed."

}


  parent reply	other threads:[~2002-03-11 22:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-11 21:50 [gentoo-dev] CUnit - !!! Name error in CUnit-1.0-4: multiple version parts Yannick Koehler
2002-03-11 22:02 ` Daniel Robbins
2002-03-11 23:34   ` Yannick Koehler
2002-03-12  0:15     ` Daniel Robbins
2002-03-11 22:33 ` Tod M. Neidt [this message]
2002-03-11 22:41   ` Tod M. Neidt
2002-03-11 23:36     ` Yannick Koehler

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=1015886000.610.12.camel@silica.localmosci \
    --to=tod@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /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