Thorsten Glaser <[EMAIL PROTECTED]> writes:
> Otavio Salvador dixit:
>
>>suggest you to produce a set of patches to implment it and proposed it
>>to debian-devel and then as release goal (on another thread).
>
> Hm, who is “you” in this case? For me, as mksh maintainer, it's “just”
> important that all shells that CAN be used as /bin/sh have the exact
> same set of debconf options and scripts to use that, as described in
> the tutorial, and I'd like to know a) if we're going to implement that
> and b) if so, who hacks it (so that the other shells' maintainers can
> just copy it).
By "you" I meant you, Thorsten, sorry by the confusion.
As I said I agree that it should be done but it shouldn't be discussed
on same thread as "dash as /bin/sh as goal" but in a separated one.
a) we can work to implement that and it should be very trivial to be
done except by the migration of all packages involved but since it
wouldn't break anything it could be easy to deal with
b) you can do it if you have time but I do think people must before to
agree to do that since the implementation itself isn't that difficult
> The other question is if I should continue offering the installation
> as /bin/sh in mksh _until_ that issue is solved, with the existing
> mechanism borrowed from dash.
Since you're already doing it you might provide a small code that
would be proposed as the common code for all involved shells but
again, please, let's start a new thread for it.
Besides, I do think it's off-topic for debian-release mailing list.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: [EMAIL PROTECTED] UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
