From: George Shapovalov <george@gentoo.org>
To: gentoo-portage-dev@gentoo.org, gentoo-dev@gentoo.org
Cc: Daniel Robbins <drobbins@gentoo.org>
Subject: Re: [gentoo-portage-dev] portage-ng design competition -- not yet
Date: Fri, 5 Dec 2003 12:35:43 -0800 [thread overview]
Message-ID: <200312051235.43597.george@gentoo.org> (raw)
In-Reply-To: <1070643286.6073.173.camel@ht.gentoo.org>
Hi everybody.
On Friday 05 December 2003 08:54, Daniel Robbins wrote:
> Everyone, please note above that I said "have a design competition *once
> we have the requirements finalized*." This hasn't happened yet. Please
Yes, and I apologise about that.
However as there seem to be a bit of confusion I want to emphasize again that
this is really not a design contest entry - I would be too ashaimed to
propose these few ideas I listed in the design *of the illustratory
prototype* as a portage-ng design :).
The purpose of this entry was to illustrate the capabilities of Ada language.
The intention is to bring up some information with the code that illustrates
what can be expected when you use it for people to look at and form the
opinion. I am not trying to push towards Ada-only, as it was taken on one or
two occasions :). However knowing the state of affairs with the languages and
having programmed in a few of these I felt it would be helpfull to have an
illustration up on the better practices I encountered.
Probably because of too much time spent on writing my paper (the unrelated
biophys one) I chose a bit too catchy title, for which I apologise again.
Since a few good points were brought up, that might be relevant to
requirements as well, I feel obliged to answer some of the posters (in
particular pvdabeel's) and dissolve some misconceptions (spider's are a good
example :)).
However starting a language flame war is definitely not anything I would like
to do. As such, I would prefer to keep the design discussions to
gentoo-portage-dev list. I will also answer any ada-related questions you may
have off list, except may be for one or two postings on -dev, to which I'll
reply to the list.
George
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-12-05 20:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 9:58 [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page George Shapovalov
2003-12-05 12:26 ` Paul de Vrieze
2003-12-05 21:33 ` George Shapovalov
2003-12-06 14:26 ` Paul de Vrieze
2003-12-06 19:35 ` Daniel Robbins
2003-12-06 19:41 ` Jon Portnoy
2003-12-07 0:13 ` [gentoo-portage-dev] ebuild strengths/weaknesses Daniel Robbins
2003-12-07 1:44 ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page Jason Stubbs
2003-12-07 2:39 ` George Shapovalov
2003-12-07 3:12 ` Jason Stubbs
2003-12-07 4:50 ` Ray Russell Reese III
2003-12-07 7:27 ` Daniel Robbins
2003-12-07 7:40 ` Daniel Robbins
2003-12-07 9:11 ` Kapil Thangavelu
2003-12-07 11:11 ` Paul de Vrieze
2003-12-08 16:03 ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page, ebuild conversion Sandy McArthur
2003-12-07 11:05 ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page Paul de Vrieze
2003-12-07 19:59 ` Philippe Lafoucrière
2003-12-07 20:10 ` Philippe Lafoucrière
2003-12-07 20:12 ` Jeff Smelser
2003-12-07 21:01 ` [gentoo-portage-dev] gpg signing of Manifests Douglas Russell
2003-12-07 21:53 ` Douglas Russell
2003-12-06 23:00 ` [gentoo-portage-dev] portage-ng concurse entry Was: Updated Portage project page George Shapovalov
2003-12-07 11:18 ` Paul de Vrieze
2003-12-05 16:54 ` [gentoo-portage-dev] portage-ng design competition -- not yet Daniel Robbins
2003-12-05 20:35 ` George Shapovalov [this message]
2003-12-05 21:59 ` [gentoo-portage-dev] portage-ng wish list Sandy McArthur
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=200312051235.43597.george@gentoo.org \
--to=george@gentoo.org \
--cc=drobbins@gentoo.org \
--cc=gentoo-dev@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