From: Chris <cjw2004d@comcast.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] A question regarding non-Portage software...
Date: Sat, 10 Mar 2007 23:25:24 -0500 [thread overview]
Message-ID: <45F384B4.7030001@comcast.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello Everyone,
I will begin by stating my problem. I have the source code (in
*.tar.bz2 format) for a couple of pieces of software that are not in the
Portage tree at all. I would like to compile and install them in such a
way that I can use them, and even so Portage recognizes them.
I have read the official Gentoo documentation regarding Portage, ebuilds
and diverting from the Portage tree and while it gave me some ideas, it
really didn't fully answer the question of exactly *how* to do what I want.
I am hoping that someone can provide me with resources - examples and/or
a walkthrough would be especially helpful. I realize that the Gentoo
team can only do so much and carefully test each package before putting
it in the official tree. There are just some pieces of software that I
want that are not even in the testing tree.
Regards,
Chris
-----BEGIN PGP SIGNATURE-----
iD8DBQFF84SxUx1jS/ORyCsRCIN+AKCR0FGCbhCPWxxQ2MEx/iCV6f03LQCeN01k
DghUTP3DSTnzDn12uTLCIWs=
=ov0z
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2007-03-11 4:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 4:25 Chris [this message]
2007-03-11 5:10 ` [gentoo-user] A question regarding non-Portage software Bo Ørsted Andresen
2007-03-11 8:47 ` Neil Bothwick
2007-03-12 7:44 ` Nick Rout
2007-03-11 5:19 ` [gentoo-user] " »Q«
2007-03-12 9:47 ` Masood Ahmed
2007-03-11 5:21 ` [gentoo-user] " Michael [Plouj] Ploujnikov
2007-03-11 14:01 ` [gentoo-user] " Steve Long
2007-03-11 19:17 ` Bo Ørsted Andresen
2007-03-11 16:05 ` [gentoo-user] " Alex Schuster
2007-03-12 18:52 ` Alan McKinnon
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=45F384B4.7030001@comcast.net \
--to=cjw2004d@comcast.net \
--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