I may not have interpreted your message correctly. If I inferred something
from it that you didn't intend to convey, please clarify.
Developing the Portage software itself is an entirely different process than
creating an ebuild: unless you're planning to contribute enhancement code to
Ned Ludd wrote:
On Sun, 2005-06-05 at 16:22 +0200, Diego 'Flameeyes' Pettenò wrote:
Currently pam stuff (implementations, modules) are organized in the worst way
I ever seen.
Most of them are in sys-libs, some of them in app-admin, other in app-crypt,
pam_smb in net-misc and so on.
I think
Nathan L. Adams wrote:
Then why is their a browsable Categories link on the packages site?
http://packages.gentoo.org/categories/
Very good question , ..
I don't agree with Ned. Organizing the packages logically makes things
less confusing for the end-user and developers alike and
Hello guys,
I've been using gentoo for 2 years now and I'm really found of this
distrobution , never touched an other distro since then.
Lately I've been creating some small probably meaningless ebuilds for
several packages like tinyscheme and adding some bug reports etc ..
I'm also looking into
Mike Frysinger wrote
you can join #gentoo-dev and we dont mind giving voice to people who are
interested in joining development ...
I'm there most of the time my nick is eniac.
the first step to becoming a dev really is to figure out *what* you want to
work on ... after that it's pretty
Chris White wrote:
Hi guys,
Well, I was working on my bashrc one day and thought, gee, would be
nice for other people to know what the heck is going on too!. Well, I
decided to go ahead and do that :P. So, here we go, a mini bashrc HOWTO
(note this only works on the latest stable
Alec Warner wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonas Geiregat wrote:
snip ChrisWhite
I gave this a quick look, and aren't you talking about bash scripts in
general rather then .bashrc files using /etc/portage/bashrc as reference
for this document.
Also I can't see the real
Hi,
I've presented this problem already to 2 developers, both of them where
unable to help me.
I hope I can find a solution on this list.
I've created my first ebuild, I've included the ebuild script the patch
and the output of the emerge tinyscheme command.
The problem is with the install -g
Fredrik Tolf wrote:
Hi List!
This is probably a FAQ, but I really couldn't find the answer. I've
STFW'd, RTFM'd and RTFDeveloper's Handbook, but I still have no answer.
The thing is, I've got a li'l program of mine that I'd like to have in
portage. I've written an ebuild and all (which works
