On 8/1/06, Jeroen Roovers <[EMAIL PROTECTED]> wrote:
# emerge --submit-info
* sys-apps/portage generates emerge --info output and uploads it
relatively tamper-proof to tickets.g.o, and
* returns a ticket to the user, a unique number that he or she can
communicate to developers and active users through a URL like
http://tickets.g.o/#ticket-number.
* --submit-info includes information about the emerge commandline that
was run last and what category/package/version emerge was
building/installing at the time.
Like you, I'm not sure this is necessary, but I like it. I like it
even more when I think that the flags and other configuration options
that are in make.conf at the time you 'emerge --info' are not
necessarily the same as those you used when, maybe a long time ago,
you emerged the dependencies of the package that breaks. Let's imagine
we have :
# emerge --submit-info package-that-breaks
If that creates a compressed tarball of all (or selected relevant)
data in /var/db/pkg concerning all packages that package-that-breaks
depends on, I like it a lot. This will give more useful information
than 'emerge --info'. And I'm not only thinking of forged 'emerge
info', but also of those users and developers that play with flags
because they like it or have to, and then forget to revert to safe
flags. I'm sure there are many legitimate ways to make such mistakes.
You end up having some parts of your system built with stupid flags,
and you don't feel guilty about it because you don't even know (this
happened to me already).
So yes, I'd love to see something like this someday. And I'd love to
help implementing it if such a decision was taken. But the question
remains : it obviously looks useful, but do we need it ?
Denis.
--
[email protected] mailing list
