From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: no ebuild what to do?
Date: Fri, 30 Sep 2005 14:27:55 +1200 [thread overview]
Message-ID: <20050930141919.AF24.NICK@rout.co.nz> (raw)
In-Reply-To: <loom.20050930T035121-141@post.gmane.org>
Forgive me for saying so, but this ebuild seems a little off to me:
1. why install to /opt?
2. DEPEND s on a lot of optional stuff from my quick read of the dekagen docs this morning. Can you do DEPEND with alternatives? like
DEPEND bladeenc|lame|vorbistools
3. aren't all the DEPENDS actually RDEPENDS as nothing at all is needed
to compile/install the program, other than bash and man which I believe
should always be present.
But I am open to education on these issues :-)
(By the way congratulations on the quick work, I started to do the same
thing, and got waylaid by my real employment :-)
On Fri, 30 Sep 2005 02:04:04 +0000 (UTC)
Greg Yasko wrote:
> There is now an ebuild in Gentoo's bugzilla, so you could use Portdir_Overlay
> and provide some much needed testing.
>
> I'd link to the Gentoo Wiki for how to do it but it's been spammed, so here goes
> & of course do the commands without the quotes:
>
> Set PORTDIR_OVERLAY in /etc/make.conf to /usr/local/portage
>
> Download dekagen-1.0.2.tar.gz and move it to /usr/portage/distfiles
>
> Login as root and do a "mkdir -p /usr/local/portage/app-cdr/dekagen"
>
> Then cd to the dekagen directory you just created.
>
> Run "ebuild dekagen-1.0.2.ebuild digest" in the dekagen directory.
>
> Add "app-cdr/dekagen ~x86" to /etc/portage/package.keywords
>
> Finally, do an "emerge dekagen" and it should work.
>
> Good luck.
>
> -G.Y.
>
> --
> gentoo-user@gentoo.org mailing list
--
Nick Rout <nick@rout.co.nz>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-30 2:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 17:18 [gentoo-user] no ebuild what to do? maxim wexler
2005-09-29 17:30 ` A. Khattri
2005-09-29 17:30 ` Michael Crute
2005-09-29 17:37 ` Dave Nebinger
2005-09-29 18:19 ` Yoandy Rodriguez
2005-09-29 22:05 ` Nick Rout
2005-09-30 2:04 ` [gentoo-user] " Greg Yasko
2005-09-30 2:12 ` Greg Yasko
2005-10-01 20:54 ` maxim wexler
2005-10-02 4:38 ` Nick Rout
2005-09-30 2:27 ` Nick Rout [this message]
2005-09-30 2:36 ` Greg Yasko
2005-09-30 3:59 ` Nick Rout
2005-10-01 17:50 ` maxim wexler
2005-10-01 18:20 ` maxim wexler
2005-10-03 10:53 ` Neil Bothwick
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=20050930141919.AF24.NICK@rout.co.nz \
--to=nick@rout.co.nz \
--cc=gentoo-user@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