| 1 |
-----BEGIN PGP SIGNED MESSAGE-----
|
| 2 |
Hash: SHA1
|
| 3 |
|
| 4 |
On Wed, 26 Sep 2007 13:42:08 -0700
|
| 5 |
Donnie Berkholz <dberkholz@g.o> wrote:
|
| 6 |
|
| 7 |
> On 16:11 Wed 26 Sep , Mike Frysinger wrote: |
| 8 |
> > On Wednesday 26 September 2007, Christian Faulhammer wrote: |
| 9 |
> > > Joe Peterson <lavajoe@g.o>: |
| 10 |
> > > > Thanks for the tip. I added "failed to install genlop (via dobin)" - |
| 11 |
> > > > not sure if there is a standard way to do this, as it seems many |
| 12 |
> > > > ebuilds just do "dobin failed", and some do "failed to install ...". |
| 13 |
> > > |
| 14 |
> > > It is mainly to localise which die command caused the halt. So I know |
| 15 |
> > > of no standard. |
| 16 |
> > |
| 17 |
> > if there is just one call to die in a function, then i usually dont bother ... |
| 18 |
> > but if there are multiple ones (possibly nested), then it can easily save |
| 19 |
> > time |
| 20 |
> |
| 21 |
> Cardoe was just telling me that die messages are not that useful or |
| 22 |
> time-saving because portage posts the line number of the failure |
| 23 |
> already. That prompts the question, should we get rid of die messages? |
| 24 |
> |
| 25 |
> Thanks, |
| 26 |
> Donnie |
| 27 |
|
| 28 |
No. They might contain useful information. Just the line
|
| 29 |
number of the failure is just frustrating: You don't really
|
| 30 |
necessarily know what went wrong, and you have to go read the ebuild to
|
| 31 |
find out. Users might not appreciate that.
|
| 32 |
> -- |
| 33 |
> gentoo-dev@g.o mailing list |
| 34 |
> |
| 35 |
Regards,
|
| 36 |
|
| 37 |
- --
|
| 38 |
Ferris McCormick (P44646, MI) <fmccor@g.o>
|
| 39 |
Developer, Gentoo Linux (Sparc, Devrel)
|
| 40 |
-----BEGIN PGP SIGNATURE-----
|
| 41 |
Version: GnuPG v1.4.7 (GNU/Linux)
|
| 42 |
|
| 43 |
iD8DBQFG+sspQa6M3+I///cRAr1QAJ9e1rGHNFBavGgR7pIxr1Xzaw12GgCg4lAK
|
| 44 |
k5/iP9fH0kcmYlBdjTKcYrY=
|
| 45 |
=BEej
|
| 46 |
-----END PGP SIGNATURE-----
|
| 47 |
éí¢‡^¾§¶Š(® šŠX§‚X¬ |
Archives