public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Secure Gentoo - What do you think?
Date: Thu, 10 Jan 2002 17:23:33 +0200	[thread overview]
Message-ID: <0GPQ005AXB2AE0@mxout1.netvision.net.il> (raw)
In-Reply-To: <20020110112447.GB610@prosalg.no>

On Thursday 10 January 2002 13:24, you wrote:
> From what I have understood, eclasses is primarily about bringing a few of
> the OOP principles to bash scripts. As a computer-linguist, I find this
> attempt misguided at best, but as a system administrator/bash script
> hacker, I find the idea appealing.
Well, it's priamrily about bringing one principle to bash, and that is code 
reuse (which isn't even strictly OOP). Things like variable scope/visibility 
(which doesn't really exist in bash) tend to poke spikes into the wheels. 

>
> Since eclasses are associated with a learning curve, would it not be
> preferrable to recast the whole inheritance thing in a proper
> object-oriented language and rather build a support framework for it there
> ?
Well, the big idea behind ebuilds in general is to make them as similar to 
compiling a package by hand (i.e. from a bash shell) as possible. Of course, 
eclasses are already sufficiently unlike that, but moving to python would 
still make things worse. For one thing, not everyone knows python as well as 
they do bash (me included).

I think that right now I should update/cleanup the eclass howto. I'll make a 
short, readable document. So, to work :-)


-- 
Dan Armak
Gentoo Linux, Desktop Team
Matan, Israel




  parent reply	other threads:[~2002-01-10 15:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07 16:13 [gentoo-dev] Secure Gentoo - What do you think? Joachim Blaabjerg
2002-01-07 16:29 ` Daniel Robbins
2002-01-07 16:31 ` Grant Goodyear
2002-01-07 16:37 ` Geert Bevin
2002-01-07 16:43 ` Tod M. Neidt
2002-01-08  0:33 ` Jano Lukac
2002-01-08  7:22   ` AW: " Sebastian Werner
2002-01-08 10:51 ` Mikael Hallendal
2002-01-08 11:14   ` AW: " Sebastian Werner
2002-01-08 13:27   ` Joachim Blaabjerg
2002-01-08 15:27     ` Grant Goodyear
2002-01-08 18:18       ` Joachim Blaabjerg
2002-01-08 18:42         ` Tod M. Neidt
2002-01-08 15:54     ` Damon M. Conway
2002-01-08 16:00       ` Mikael Hallendal
2002-01-08 17:10         ` Damon M. Conway
2002-01-08 17:15           ` Mikael Hallendal
2002-01-08 18:11             ` Damon M. Conway
2002-01-08 23:35               ` Mikael Hallendal
2002-01-10 11:24           ` Karl Trygve Kalleberg
2002-01-10 11:56             ` [gentoo-dev] Secure Gentoo - OO-ebuilds Einar Karttunen
2002-01-10 15:23             ` Dan Armak [this message]
2002-01-10 13:51 ` [gentoo-dev] Secure Gentoo - What do you think? Joachim Blaabjerg
2002-01-10 14:40   ` Mikael Hallendal
2002-01-10 15:00     ` Joachim Blaabjerg
2002-01-10 15:27       ` AW: " Sebastian Werner
2002-01-10 17:09       ` Joachim Blaabjerg
2002-01-10 18:48         ` Daniel Robbins
2002-01-11 19:07         ` Sebastian Werner
2002-01-11 20:07           ` Joachim Blaabjerg
2002-01-10 18:28       ` Martin Schlemmer
2002-01-10 18:49   ` Grant Goodyear

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=0GPQ005AXB2AE0@mxout1.netvision.net.il \
    --to=danarmak@gentoo.org \
    --cc=gentoo-dev@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