public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Karl Trygve Kalleberg <karltk@prosalg.no>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Secure Gentoo - What do you think?
Date: Thu, 10 Jan 2002 12:24:47 +0100	[thread overview]
Message-ID: <20020110112447.GB610@prosalg.no> (raw)
In-Reply-To: <20020108171039.5545B255A8@chiba.3jane.net>

On Tue, Jan 08, 2002 at 11:10:39AM -0600, Damon M. Conway wrote:
>  Mikael Hallendal wrote:
> >tis 2002-01-08 klockan 16.54 skrev Damon M. Conway:
> >
> >> I think this is where eclasses could really help.  Eclasses should allow
> >> you to create a meta ebuild that looks for certain make.conf vars set and
> >> react accordingly.  danarmak and drobbins are the ones to ask for more
> >> details on eclasses.
> >
> >For now eclasses should _only_ be used in KDE. A decission still has to
> >be made about eclasses. And both me and drobbins have some objections to
> >eclasses.
> 
> Hmm, ok.  I thought they were on their way to finalization.
> 
> >For one I think that eclasses break one of ebuilds most important
> >strength. The ease of use, that they are almost identical to installing
> >a package manually.
> 
> Depends on usage.  I think eclasses could be quite powerful for
> cross-platform capabilities and system types (SuxOS, Web Server, etc), and
> they, in theory, can pick up the global configuation baton where make.conf
> leaves off.  As long as they are well-defined, I don't see how they really
> cause any problems, or make ebuilds any harder to write.

>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.

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
? 

For instance, use scsh (okay, okay, so Scheme might not be popular with
the crowd) or Python. If you take a look at SCons, you'll see Make recast
into Python, with all the benefits that gives you (stable, clean,
well-known language, lots of documentation, lots of support libraries,
cross-platform runtime).

Just stirring things up since the eclasses debate seems to be coming
regardless.


Karl T


  parent reply	other threads:[~2002-01-10 11:40 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 [this message]
2002-01-10 11:56             ` [gentoo-dev] Secure Gentoo - OO-ebuilds Einar Karttunen
2002-01-10 15:23             ` [gentoo-dev] Secure Gentoo - What do you think? Dan Armak
2002-01-10 13:51 ` 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=20020110112447.GB610@prosalg.no \
    --to=karltk@prosalg.no \
    --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