os metadata / getting rid of enums
jon at vmware.com
Wed Dec 18 23:06:28 UTC 2002
On Wed, 2002-12-18 at 14:48, Joel Peshkin wrote:
> As Gerv points out, doing this with a strict hierarchy can be done by
it could, but it doesn't seem as clean. and it wouldn't work in every
case. Shouldn't OSX show up under "BSD"? Also, we'd have to start using
OS names like this:
Red Hat 7.2 Linux
Solaris 2.5.1 SysV
OSX 10.2 BSD
etc. I think this would be a quick fix, but not necessarily address the
issues i'm having.
> But... when this is something that wants to be effectively a multiple
> select, is there a broader need for it?
I think there is. You mentioned the arch field, which is another good
example of this. Selecting "x86" should match "Athlon XP 2100", "VIA C3
800", and "Pentium 4 2.8ghz w/ HT".
This isn't particularly complex code to write, and doesn't really
require that many changes overall. off the top of my head, we'd need to
change how @legal_opsys is defined, change Bugzilla::Search to
comprehend these "effective multiple selects", add the op_sys table, and
add edit[opsys|arch].cgi to allow maintenance. I'll probably have this
finished in a day or two here, so for now i'll do this against cvs and
send the results out.
there are a few bugs that could have relevance here, but none seem to
specifically address the os or arch fields:
Engineering System Administrator
"Te occidere possunt sed te edere non possunt nefas est."
More information about the developers