* [gentoo-dev] emerge feature for 1.0 release?
@ 2002-03-13 21:43 Zach Forrest
2002-03-13 22:00 ` Bart Verwilst
0 siblings, 1 reply; 3+ messages in thread
From: Zach Forrest @ 2002-03-13 21:43 UTC (permalink / raw
To: gentoo-dev
I think it would be nice to add something like the code below to the
emerge command before the 1.0 release of Gentoo. Then rather than Python
printing a traceback on a keyboard interrupt (i.e. ^C), a nice "abort"
message would be printed. This would be more refined from a user
perspective (in my opinion). Of course, if the '--debug' option were to
be passed to emerge, the trace back could/should be printed.
if __name__ == '__main__':
# Replace this with however emerge needs to be called.
app = EmergeApp()
try:
app.main()
except KeyboardInterrupt, e:
print 'emerge: aborted'
zach
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] emerge feature for 1.0 release?
2002-03-13 21:43 [gentoo-dev] emerge feature for 1.0 release? Zach Forrest
@ 2002-03-13 22:00 ` Bart Verwilst
2002-03-13 23:13 ` Zach Forrest
0 siblings, 1 reply; 3+ messages in thread
From: Bart Verwilst @ 2002-03-13 22:00 UTC (permalink / raw
To: gentoo-dev
Hi!
in the latest 1.8.9_pre's, this is already implemented, 1.8.8 doesn't have
this functionality yet though..
See ya!
On Wednesday 13 March 2002 22:43, Zach Forrest wrote:
|| I think it would be nice to add something like the code below to the
|| emerge command before the 1.0 release of Gentoo. Then rather than Python
|| printing a traceback on a keyboard interrupt (i.e. ^C), a nice "abort"
|| message would be printed. This would be more refined from a user
|| perspective (in my opinion). Of course, if the '--debug' option were to
|| be passed to emerge, the trace back could/should be printed.
||
|| if __name__ == '__main__':
|| # Replace this with however emerge needs to be called.
|| app = EmergeApp()
|| try:
|| app.main()
|| except KeyboardInterrupt, e:
|| print 'emerge: aborted'
||
||
|| zach
||
|| _______________________________________________
|| gentoo-dev mailing list
|| gentoo-dev@gentoo.org
|| http://lists.gentoo.org/mailman/listinfo/gentoo-dev
--
Bart Verwilst
Gentoo Linux Developer, Desktop Team
Gent, Belgium
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] emerge feature for 1.0 release?
2002-03-13 22:00 ` Bart Verwilst
@ 2002-03-13 23:13 ` Zach Forrest
0 siblings, 0 replies; 3+ messages in thread
From: Zach Forrest @ 2002-03-13 23:13 UTC (permalink / raw
To: gentoo-dev
Cool, man. (Thanks)
Bart Verwilst wrote:
> Hi!
>
> in the latest 1.8.9_pre's, this is already implemented, 1.8.8 doesn't have
> this functionality yet though..
>
> See ya!
>
> On Wednesday 13 March 2002 22:43, Zach Forrest wrote:
> || I think it would be nice to add something like the code below to the
> || emerge command before the 1.0 release of Gentoo. Then rather than Python
> || printing a traceback on a keyboard interrupt (i.e. ^C), a nice "abort"
> || message would be printed. This would be more refined from a user
> || perspective (in my opinion). Of course, if the '--debug' option were to
> || be passed to emerge, the trace back could/should be printed.
> ||
> || if __name__ == '__main__':
> || # Replace this with however emerge needs to be called.
> || app = EmergeApp()
> || try:
> || app.main()
> || except KeyboardInterrupt, e:
> || print 'emerge: aborted'
> ||
> ||
> || zach
> ||
> || _______________________________________________
> || gentoo-dev mailing list
> || gentoo-dev@gentoo.org
> || http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-03-13 23:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-03-13 21:43 [gentoo-dev] emerge feature for 1.0 release? Zach Forrest
2002-03-13 22:00 ` Bart Verwilst
2002-03-13 23:13 ` Zach Forrest
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox