From: Jason Stubbs <jasonbstubbs@mailandnews.com>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] Re: [gentoo-dev] Web-based Portage Frontendg
Date: Sat, 29 Nov 2003 23:46:16 +0900 [thread overview]
Message-ID: <200311292346.16736.jasonbstubbs@mailandnews.com> (raw)
In-Reply-To: <20031127084244.GA29988@unm.edu>
On Thursday 27 November 2003 17:42, Jason Mobarak wrote:
> Somethings you need to do to get up to speed on unit tests:
>
> 1) Read the documentation for the unittest module in the Python standard
> library.
> 2) Read http://pyunit.sourceforge.net/pyunit.html
> 3) Get a CVS CO of Twistedmatrix.com's CVS and look over how they do there
> unit tests, they use their own implementation of unittest but the
> differences are minor
All complete. I didn't read every line of twisted's unittests but I get the
idea. I've also kept it for a reference.
> On 17:03 Thu 27 Nov , Jason Stubbs wrote:
> > I think there's two ways to attack it:
> >
> > a) I work through documenting everything while you work through
> > separating everything that's documented. Once the documenting is done, I
> > can begin unit testing and you can join me once the separation is done.
> > b) You document and separate and I unit test what has been completed.
>
> I like (b),
>
> > BTW, will this work become redundant by portage-ng?
>
> I hope after portage is separated into a library the code can be
> incorporated into "portage-ng", we could very well be working on the
> beginnings of the next generation of portage. I want to add "layers" to how
> everything interacts, key design patterns being heavy focusing on "plug-in"
> orientation and model-view-control. Some keywords you should research if you
> are interested in this are Mix-In style programming and the use of
> interfaces to abstract aggregate interaction between sections of a program.
>
> "Portage-ng" is being touted as a complete rewrite currently (from what I
> remember) and it seems senseless to throw away the 10k lines of code that
> make up the current portage system.
Well, it seems it is a complete redesign from scratch, but the complete
rewrite will be much longer coming. If you are still interested in continuing
your work, I'm still interested in helping. If we do it properly, it should
not be too difficult to remodel it to fit the design spec of portage-ng once
it is completed. The components can be replaced by more advanced versions
later if need be, but as you say there's no point in throwing 10k lines of
code away.
Regards,
Jason Stubbs
--
gentoo-portage-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-11-29 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1069588805.28236.17.camel@antares.hausnetz>
[not found] ` <200311271548.01028.jasonbstubbs@mailandnews.com>
[not found] ` <20031127065907.GA28671@unm.edu>
[not found] ` <200311271703.47562.jasonbstubbs@mailandnews.com>
2003-11-27 8:42 ` [gentoo-portage-dev] Re: [gentoo-dev] Web-based Portage Frontendg Jason Mobarak
2003-11-27 9:07 ` [gentoo-portage-dev] Portage Modularisation Jason Stubbs
2003-11-29 14:46 ` Jason Stubbs [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=200311292346.16736.jasonbstubbs@mailandnews.com \
--to=jasonbstubbs@mailandnews.com \
--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