> On Monday 31 August 2009, Yann Dirson wrote: >> This seems to be similar to #480533, which was apparently fixed by >> moving more stuff to perl-base. > > I very much doubt it is related as the version of perl that fixed #480533 > is ancient (included in stable). So if that change had fixed it, then I > would never have seen the problem when I did. > > It may be that *a* solution to this issue could be to move yet more stuff > to perl-base, but I doubt that is desirable. > > IMO console-setup should, if at all possible, make sure that it only uses > functions available in current perl-base. Neither extending perl-base, > nor having console-setup depend on perl are desirable solutions.
If I understand correctly what happened with #480533, it was a utf8-related module that was already part of perl-base, which suddenly gained dependencies it did not have prior to that. I thought we could be hitting the same problem again. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
