Summary: | package specifier field to make wranger's work easier | ||
---|---|---|---|
Product: | Gentoo Infrastructure | Reporter: | Robin Johnson <robbat2> |
Component: | Bugzilla | Assignee: | Jeffrey Forman (RETIRED) <jforman> |
Status: | RESOLVED LATER | ||
Severity: | enhancement | CC: | dberkholz |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 92449 |
Description
Robin Johnson
![]() ![]() ![]() ![]() Robin, Could you provide some sort of example from another bugzilla to do this? At this point, I'm not going to be adding fields into the bugzilla install, that is a far-down-the-road priority to be honest. I want to get the new install installed first, since it has a ton of security fixes. Then I can handle feature enhancement requests. -Jeffrey Robin, After thinking about this for a bit today...couldnt a hacky php or perl app be written which calls on packages.g.o to grab the package? Rather than integrating something totally into bugzilla. Jeff: basically all I'm looking for is a single text field that users can put the name(s) of the involved packages in. eg a user with a problem between Amanda and Tar would put in "=app-admin/amanda-2.3* =sys-apps/tar-1.5*" Ahh, i see what you mean, thats a perfectly valid idea. I will dig deeper into how far I can customize bugzilla, and how much fu will be necessary to add a custom field into the db. But I make no promises on whether it gets into our upgrade initially. -Jeff This is just something that's going to be added later. |