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