public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Firefox
Date: Sat, 04 Feb 2006 20:01:43 +0100	[thread overview]
Message-ID: <43E4FA17.6090006@planet.nl> (raw)
In-Reply-To: <200602041202.43655.ddjones@riddlemaster.org>

Daniel D Jones schreef:
> On Saturday 04 February 2006 11:37, Holly Bostick wrote:
> 
>> If an ebuild doesn't say it's compiling from CVS, it isn't. And of 
>> course, you can always just open it in a text editor and /look/...
>> 
> 
> I'm still learning how Portage works.  I wasn't aware that ebuilds 
> were that straightforward.

Well, in some respects they aren't, insofar as you kinda need to be
familiar with the compilation process of the program under
consideration, on the one hand (for example, the specific dependencies,
and the configuration options for it, which obviously vary from
application to application), and Gentoo conventions on the other hand
(such as the variables used to specify things like version number and
install directory and the like).

But in the sense that they are ultimately just scripts, and scripts are
ultimately just text, which are quite understandable if you know the
"language" they're written in, yes, ebuilds are very much "that
straightforward". Certainly straightforward enough even for the
completely untutored to be able to see things like where the source
is being downloaded from (the project site, or a gentoo mirror or
someplace else), and what options the application is being configured
with (or not), and how the USE flags available relate to the configure
options available to the application.

That's what makes Gentoo so cool-- or at least one of the big things-- *I*
can write an ebuild, at need, and I can't code my way out of a paper
bag. A *wet* paper bag. Admittedly, my skills only really reach (at this
time) to modifying existing ebuilds in relatively simple ways (version
bumps and "switching" annoying dependencies to separate-but-equal ones),
but I can learn more via the docs when I want to try something more
complex.  I can even submit modified or new ebuilds on b.g.o for
submission into Portage (and have done, actually).

It's just me (same old me), but I can provide development services even
now, as I am (which is way more than anyone ever 'asked' of me under
previous distros, or under Windows, and certainly more than I ever knew
I was capable of), and I can fairly easily learn enough to do more, if I so
choose, by reading the Development docs on the main site, which will
tell you all you need to know about getting started with ebuilds.

Everybody can really help, in a truly functional way, and that's because
ebuilds *are* in that sense simple enough that they give you a "way in",
if you see what I mean.

Holly
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-02-04 19:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-04 13:09 [gentoo-user] Firefox Daniel D Jones
2006-02-04 13:26 ` Beau E. Cox
2006-02-04 14:09   ` Daniel D Jones
2006-02-04 16:37     ` Holly Bostick
2006-02-04 17:02       ` Daniel D Jones
2006-02-04 18:20         ` Chan Min Wai
2006-02-04 19:40           ` [gentoo-user] Firefox Simon Kellett
2006-02-05 17:21             ` Roy Wright
2006-02-04 19:01         ` Holly Bostick [this message]
2006-02-04 13:30 ` [gentoo-user] Firefox Andrew Gaydenko
2006-02-04 13:32 ` Holly Bostick
2006-02-04 13:36 ` Scott Stoddard
  -- strict thread matches above, loose matches on Subject: below --
2011-06-27 23:52 Daniel D Jones
2011-06-28  0:44 ` Albert Hopkins

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=43E4FA17.6090006@planet.nl \
    --to=motub@planet.nl \
    --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