| 1 |
On Thu, Jan 5, 2017 at 11:27 PM, Kent Fredric <kentnl@g.o> wrote: |
| 2 |
> |
| 3 |
> If packages had a field called "BUGS=" it could contain an array of |
| 4 |
> bugs a package is known to contain, but can be conditionally avoided if |
| 5 |
> you're careful. |
| 6 |
> |
| 7 |
> Packages with non-empty BUGS= fields would be treated as hard-masked |
| 8 |
> for the purpose of repoman checks, and so packages that depend on |
| 9 |
> specific version ranges of packages with BUGS= fields are invalid, |
| 10 |
> and need their own BUGS= fields. |
| 11 |
> |
| 12 |
|
| 13 |
So, while I'm not sure if this is the best way to go about it, I think |
| 14 |
what it does point to is there being possible benefit in creating a |
| 15 |
closer link between our repository and bug trackers. |
| 16 |
|
| 17 |
We've seen this come up in managing stable requests as well (having |
| 18 |
users be able to vote on things, having automated testing, etc). |
| 19 |
|
| 20 |
With the recent stable changes we have bugs being tagged with "atoms." |
| 21 |
With your proposal we have ebuilds being tagged with bugs. |
| 22 |
|
| 23 |
I can see benefits to having a single way to associate bugs and |
| 24 |
ebuilds, and making those associations available to bug trackers and |
| 25 |
package managers. |
| 26 |
|
| 27 |
I think the question is: |
| 28 |
1. What is the best way to go about this? |
| 29 |
2. Is anybody actually going to make use of this? |
| 30 |
|
| 31 |
The intended use cases in #2 probably will influence #1. However, it |
| 32 |
doesn't make sense to have multiple ways of doing these associations, |
| 33 |
because bugzilla doesn't know anything about the repo, and portage |
| 34 |
doesn't know anything about bugzilla. Having one place to store the |
| 35 |
associations and tools to make that information accessible elsewhere |
| 36 |
makes more sense. |
| 37 |
|
| 38 |
-- |
| 39 |
Rich |
Archives