public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brett I. Holcomb" <brettholcomb@charter.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ebuild creation assistance...
Date: Sat, 8 May 2004 22:40:07 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0405082236530.18662@strider> (raw)
In-Reply-To: <409D9639.8030504@indiana.edu>

On Sat, 8 May 2004, John David Ratliff wrote:
Check the docs on the Gentoo site for nameing convention.  I ran into this 
on an ebuild - currently emerge can't handle some of the names that are 
used.  As long as the various ${P} ${PN} variables get set correctly in 
the ebuild you and change the name as you suggest.  Whether or not it 
works depends on how the source you're getting it from stores it.  I had 
one where the source needed the extra version info to retrieve it properly 
but portage wouldn't handle it  


 > Brett I. Holcomb 
wrote: > 
> >To just create an ebuild you don't need to check out the portage tree.  
> >
> >  
> >
> Thanks. This is mostly what I have done.
> 
> Another question. What is wrong with this name for an ebuild
> 
> tigcc-0.95_beta8r1.ebuild
> 
> The version is 0.95 beta 8r1 (This is what they call it).
> 
> Remove the r1, and there are no problems. Should I just change it to 
> maybe tigcc-0.95_beta8.ebuild
> 
> Thanks...
> 
> >
> > On Sat, 8 May 2004, John David Ratliff wrote:
> >
> >  
> >
> >>I want to create an ebuild for a software package, but I am confused on 
> >>the directions. The ebuild HOWTO tells me to checkout portage from CVS, 
> >>however, it lists no CVS server or what kind of authentication to use. 
> >>Is this restricted to 'official' developers? If so, can I still create 
> >>and submit an ebuild? If not, what is the CVSROOT setting so I can 
> >>checkout portage?
> >>
> >>I also need to add the software to the gentoo mirrors. I read in one of 
> >>the HOWTOs that cvs snapshots could be added to the mirror. This is 
> >>similar, except they use the same filename for every new version, so 
> >>there is no way to know which version you are downloading from their 
> >>site. Additionally, each new version requires different a specific 
> >>version of another package to be downloaded, so it is crucial that the 
> >>version of the original package is known. So I thought maybe I could add 
> >>this with a version number to the gentoo mirror.
> >>
> >>Finally, I am unsure where in portage it should be added. It is a 
> >>cross-compiler for C into native binaries for a specific kind of 
> >>calculator. The software is a modified version of GCC and binutils.
> >>
> >>Thanks...
> >>
> >>
> >>--
> >>gentoo-dev@gentoo.org mailing list
> >>
> >>    
> >>
> >
> >  
> >
> 
> 
> --
> gentoo-dev@gentoo.org mailing list
> 

-- 
Brett I. Holcomb

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2004-05-09  2:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-09  1:21 [gentoo-dev] ebuild creation assistance John David Ratliff
2004-05-09  1:40 ` Brett I. Holcomb
2004-05-09  2:23   ` John David Ratliff
2004-05-09  2:36     ` Peter Ruskin
2004-05-09  2:40     ` Brett I. Holcomb [this message]
2004-05-09  2:57       ` John David Ratliff
2004-05-09  3:05         ` George Shapovalov
2004-05-09  7:05     ` Drake Wyrm
2004-05-09 19:48 ` Joseph Booker

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=Pine.LNX.4.58.0405082236530.18662@strider \
    --to=brettholcomb@charter.net \
    --cc=gentoo-dev@lists.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