From: Robert Cole <robert.cole@support4linux.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] creating ebuilds
Date: Tue, 6 Jan 2004 16:24:53 -0800 [thread overview]
Message-ID: <200401061624.53192.robert.cole@support4linux.com> (raw)
In-Reply-To: <20040106220955.297c7663.spider@gentoo.org>
On Tue January 06 2004 1:09 pm, Spider wrote:
> 3b) QC, by developer of the strictest sense. A lot of people failto
> grasp even the most basic concepts of ebuild programming and / or the
> case of boolean logic. ( if foo then bar ; then baz..... or was that or
> baz? or ... or.... if foo then bar... then we ignore the case of not
> foo? )
>
> > ** Assuming everything is perfect
> > a. Ebuild works fine, no patches need to be applied/software is now
> > known stable.
>
> No. its not, we have yet no conclusion as to wether the build is
> complete or not. Does it build all documentation? are the files really
> with that license? are the dependencies correct according to
> configure.* or did it just happen to work on a fully installed system?
>
> Is all functionality accounted for in the dependencies, or will it build
> without, say X, but with reduced functionality? None of this is checked
> for, and almost none of them are accountable by automagic.
I guess I think a little differently in that my response to the above is: You
mean ebuild creators don't already do this?
I don't say that to be funny, honest. I just can't seeing letting ANYONE even
see an ebuild I create without having done all those checks in the first
place! Then after that I would give it to my sponsor to give a brutal
evaluation of it and then and only then after further changes and testing
would I ask it to be included in the tree.
I don't know maybe I'm wierd or something it just comes from my early
programming instructors in the mid 80s, document, document, document, test,
test, test and then test some more.
> Conclusion : please, write a GLEP. i want to see this discussed more,
> but in a whole new thread.
Agree this thread is dead.
I feel I got a much better understanding of the whole gentoo dev process and I
feel it was pretty good and most of it was useful back and forth. Overall a
decent thread I think. Lets all just try to relax now. :) Let's go back to
playing nice in the sandbox :)
BTW, Happy new year!
Robert
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-01-07 0:25 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 7:05 [gentoo-dev] creating ebuilds Robert Cole
2004-01-06 7:15 ` Jon Portnoy
2004-01-06 7:36 ` Allen Parker
2004-01-06 7:39 ` Robert Cole
2004-01-06 7:55 ` Jon Portnoy
2004-01-06 8:39 ` Robert Cole
2004-01-06 9:54 ` Kurt Lieber
2004-01-06 13:08 ` Caleb Tennis
2004-01-06 14:13 ` Allen Parker
[not found] ` <E1Adry1-0003ZV-8m@smtp.gentoo.org>
2004-01-06 21:09 ` Spider
2004-01-07 0:24 ` Robert Cole [this message]
2004-01-07 13:36 ` Chris Gianelloni
2004-01-06 15:18 ` Robert Cole
2004-01-06 16:04 ` Chris Gianelloni
2004-01-06 16:31 ` Robert Cole
2004-01-06 16:45 ` Ciaran McCreesh
2004-01-06 17:17 ` Robert Cole
2004-01-06 19:17 ` Chris Gianelloni
2004-01-06 19:43 ` Robert Cole
2004-01-06 20:07 ` Ciaran McCreesh
2004-01-08 7:12 ` John Nilsson
2004-01-08 9:56 ` Paul de Vrieze
2004-01-08 14:36 ` John Nilsson
2004-01-08 20:53 ` Nicholas Hockey
2004-01-10 11:39 ` foser
2004-01-06 12:09 ` Chris Gianelloni
2004-01-06 15:38 ` Robert Cole
2004-01-06 19:29 ` Marius Mauch
2004-01-06 12:44 ` Paul de Vrieze
2004-01-06 15:45 ` Robert Cole
2004-01-06 20:39 ` Paul de Vrieze
2004-01-06 21:11 ` [gentoo-dev] " Eamon Caddigan
2004-01-06 21:37 ` Caleb Tennis
[not found] ` <E1Adllq-0001dV-26@smtp.gentoo.org>
2004-01-06 7:46 ` [gentoo-dev] " Jon Portnoy
[not found] ` <E1AdlmM-0001xM-00@deer.gmane.org>
2004-01-07 6:18 ` [gentoo-dev] " Jeff Stuart
2004-01-07 13:20 ` Caleb Tennis
2004-01-06 18:56 ` [gentoo-dev] " George Shapovalov
2004-01-06 19:06 ` George Shapovalov
2004-01-06 19:45 ` Marius Mauch
2004-01-06 20:44 ` Paul de Vrieze
2004-01-10 11:13 ` foser
2004-01-10 12:16 ` Jason Stubbs
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 8:17 Robert Cole
2004-01-06 12:57 ` Paul de Vrieze
2004-01-06 15:37 ` Seemant Kulleen
2004-01-06 18:14 ` Robert Cole
2004-01-06 20:49 ` Jan Schubert
[not found] <E1Adlms-0007w8-Uk@smtp.gentoo.org>
2004-01-06 12:33 ` Paul de Vrieze
2004-01-06 17:26 ` Robert Cole
2004-01-06 17:39 ` Ciaran McCreesh
2004-01-06 18:01 ` Robert Cole
2004-01-06 19:26 ` Chris Gianelloni
2004-01-06 19:53 ` Peter Ruskin
2004-01-06 20:12 ` Ciaran McCreesh
2004-01-06 20:21 ` Marius Mauch
2004-01-06 20:37 ` Jan Schubert
2004-01-06 21:14 ` Chris Gianelloni
2004-01-06 21:36 ` Chris Gianelloni
2004-01-06 19:20 ` Chris Gianelloni
2004-01-06 17:56 ` Eldad Zack
2004-01-06 18:02 ` Eldad Zack
2004-01-06 18:33 ` Robert Cole
2004-01-06 19:31 ` Chris Gianelloni
2004-01-06 20:38 ` Jan Schubert
2004-01-06 20:54 ` Spider
[not found] <FILESERVERAmEaJswFC00000011@FILESERVER.aurora.local>
2004-01-06 14:57 ` Caleb Tennis
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=200401061624.53192.robert.cole@support4linux.com \
--to=robert.cole@support4linux.com \
--cc=gentoo-dev@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