| 1 |
On Wed, 07 Aug 2013 22:45:55 +1000 |
| 2 |
Michael Palimaka <kensington@g.o> wrote: |
| 3 |
|
| 4 |
> On 7/08/2013 22:18, Tom Wijsman wrote: |
| 5 |
> > We usually take it a step further, putting the actual error there; |
| 6 |
> > if the maintainer reads the error, it will be clear it failed to |
| 7 |
> > build: |
| 8 |
> > |
| 9 |
> > "=kde-base/kmail-4.8.10 with GCC 4.8 - File:Line:Char: Error: |
| 10 |
> > Reason" |
| 11 |
> |
| 12 |
> Is there any benefit to adding = in this case? |
| 13 |
|
| 14 |
Quoted that from his reply; but I confess I add this to summaries |
| 15 |
because it makes it an acceptable package atom, for scripts to use. |
| 16 |
|
| 17 |
Just an example: |
| 18 |
|
| 19 |
> # emerge 'sys-devel/gcc-4.8' |
| 20 |
> !!! 'sys-devel/gcc-4.8' is not a valid package atom. |
| 21 |
> !!! Please check ebuild(5) for full details. |
| 22 |
> |
| 23 |
> # emerge '=sys-devel/gcc-4.8' |
| 24 |
> |
| 25 |
> These are the packages that would be merged: |
| 26 |
|
| 27 |
I think the logic to automatically add '=' is not as easy as checking |
| 28 |
the first character and requires some more effort to implement; so, |
| 29 |
having usable atoms sounds like a more handy approach. |
| 30 |
|
| 31 |
If package atoms had their separate atom(s) field then this would no |
| 32 |
longer be a requirements; but until then, we can only help this way. |
| 33 |
|
| 34 |
Not sure if people actually run scripts against Bugzilla; but working |
| 35 |
towards that way should be something to consider, because it would ease |
| 36 |
to run scripts against it. One that comes to mind is to check the |
| 37 |
entire bug list (you can download those [1]) for package atoms which |
| 38 |
can no longer be satisfied; that way, you could detect some things: |
| 39 |
|
| 40 |
1. Typos in package names, this improves searching for those bugs. |
| 41 |
|
| 42 |
2. Versions no longer in the Portage tree, this helps find old bugs; |
| 43 |
as well as allows a tester to test those bugs in specific to see if |
| 44 |
they still happen for newer versions. Or ask the user to test again. |
| 45 |
|
| 46 |
3. Bugs that have already been fixed, some bugs are canonical and |
| 47 |
always use the same syntax as they are filed by other scripts; for |
| 48 |
such bugs we could check if the bug still occurs by doing a build |
| 49 |
test for them. The resources needed for this is questionable, but |
| 50 |
it's just one idea of many; all what package atoms can help do. |
| 51 |
|
| 52 |
[1]: https://bugs.gentoo.org/bots.html |
| 53 |
|
| 54 |
-- |
| 55 |
With kind regards, |
| 56 |
|
| 57 |
Tom Wijsman (TomWij) |
| 58 |
Gentoo Developer |
| 59 |
|
| 60 |
E-mail address : TomWij@g.o |
| 61 |
GPG Public Key : 6D34E57D |
| 62 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives