From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] Portage Language
Date: Fri, 28 Nov 2003 11:52:17 -0700 [thread overview]
Message-ID: <1070045537.12098.38.camel@ht.gentoo.org> (raw)
In-Reply-To: <20031128081705.GA9736@unm.edu>
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
On Fri, 2003-11-28 at 01:17, Jason Mobarak wrote:
> My opinion: Python.
First: you live in Albuquerque? :)
> Arguments for Python
> --------------------
One of the things we are trying to do this time around is to have a very
professional, well-managed development process. That process involves
writing up (excuse the "*"'s) *requirements* before selecting an
implementation language. That is, we need to decide what our goals are
before we determine the best way to reach those goals. The prolog
prototype is meant to just explore possibilities... the portage-ng code
itself will not come from this prototype.
This also means that there has been a shift in our approach, after I got
some feedback from nerdboy. We're going with a requirements-first
approach for development.
> Also, I'm working on separating portage into packages, I feel a bit disconnected
> from other developers and I'm not sure if I should just scrap what I'm doing and
> wait for portage-ng development to get under way.
What is the portage-ng list? I don't think I'm on it.
The best thing to do right now is to assist in the effort described on
the portage project page:
http://www.gentoo.org/proj/en/portage/
Specifically, the:
"24 Dec 2003
portage-ng:
public initial comprehensive requirements and design goals document"
There is no community work happening yet because there have been no
efforts from the managers to foster community development, so I'm
jumping in to get things started.
What we need to do is figure out what the requirements of the system
should be. I'll post my initial list to this list and hopefully show you
what I'm looking for, and allow you to get the ball rolling.
> So, please, advice, comments, direction. :-)
Hopefully this'll help :)
Regards,
Daniel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-11-28 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 23:17 [gentoo-portage-dev] Portage Language Thomas L. Bevan
2003-11-28 0:06 ` Daniel Robbins
2003-11-28 8:17 ` Jason Mobarak
2003-11-28 12:18 ` Philippe Lafoucrière
2003-11-28 18:52 ` Daniel Robbins [this message]
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=1070045537.12098.38.camel@ht.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-portage-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