From: "Douglas Anderson" <dja@gendja.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: equery refactorization
Date: Sun, 7 Dec 2008 12:29:35 +0900 [thread overview]
Message-ID: <efeb8d230812061929l71b02f50y2783afaedced3330@mail.gmail.com> (raw)
In-Reply-To: <493B3CAD.9070304@smith-li.com>
On Sun, Dec 7, 2008 at 12:02 PM, Michael A. Smith <michael@smith-li.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Regarding gentoolkit/trunk/src/equery/tests
>
> I discovered all the test kit that's in equery, and have been refactoring
> 'em.
> They're written in bash, not python, so they're a candidate for some kind of
> python unit testing. Right now, however, that's not a priority for me, so
> I'm
> just making the bash cleaner and hopefully faster and more maintainable. I
> think it'll be helpful as we refactor.
>
> The question is, how maintainable are the "help" tests? These are tests that
> try to confirm that the --help output of each module is correct. I think it
> might be more work than it's worth to try to maintain those...
>
> Thoughts?
I know some people like to write the tests and then write the code to
match, but I don't think it's a good idea for you to refactor the
tests as I'm refactoring the codebase :)
Especially since I'm chopping and moving things, renaming functions,
etc, as long as I think it'll help in the long term.
I even changed the format of the help output ;) Why? Because we have
two user-oriented tools with a similar "modular" design, equery and
eselect, and yet they have a totally different naming scheme and
behave quite differently. It's unnecessarily confusing so I tried to
make them more uniform (I'll upload some code shortly). I always
though equery's --help was cluttered and confusing. A complete
overview is what `man equery' is for, IMHO.
I also changed the way equery handles input slightly. For example this
I think is unnecessarily lenient and in the end confusing, because it
goes against what most other tools do (raise an exception):
$ equery -q -i list mozilla-firefox
!!! unknown global option -i, reusing as local option
So, I don't think we should be working on the tests until we have most
of the code refactored, but I re-extend my invitation for help on that
because there's quite a bit to do!
-Doug
next prev parent reply other threads:[~2008-12-07 3:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <efeb8d230812020201m3910b204q3af56b932d07cc07@mail.gmail.com>
[not found] ` <33EF1957-2481-4AF1-A112-D12D7C1119A7@smith-li.com>
2008-12-03 9:03 ` [gentoo-portage-dev] Re: equery refactorization Douglas Anderson
2008-12-04 5:43 ` Alec Warner
2008-12-06 7:33 ` Douglas Anderson
2008-12-06 23:21 ` [gentoo-portage-dev] Python style (Was: equery refactorization) Michael A. Smith
2008-12-07 0:50 ` Zac Medico
2008-12-07 4:07 ` Douglas Anderson
2008-12-07 18:10 ` Alec Warner
2008-12-06 23:32 ` [gentoo-portage-dev] Re: equery refactorization Michael A. Smith
2008-12-07 3:02 ` Michael A. Smith
2008-12-07 3:29 ` Douglas Anderson [this message]
2008-12-07 3:34 ` Michael A. Smith
2008-12-07 3:44 ` Douglas Anderson
2008-12-07 4:26 ` Marius Mauch
2008-12-07 4:54 ` Douglas Anderson
2008-12-07 7:16 ` Michael A. Smith
2008-12-07 12:28 ` Marius Mauch
2008-12-07 23:52 ` Douglas Anderson
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=efeb8d230812061929l71b02f50y2783afaedced3330@mail.gmail.com \
--to=dja@gendja.com \
--cc=gentoo-portage-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