On Sun, May 1, 2011 at 8:47 PM, Simon Josefsson si...@josefsson.org wrote:
How about just removing the module? If something breaks, the maintainer
can track it down, and will notice that the module disappeared, and fix
the package. If nothing breaks, it is normally just a portability
problem
forgot to remove 'exit' from the Dependencies: section
of other modules. I'm doing that now.
Thank you! That shouldn't have been there since it was deprecated, I
think, so a lot of projects probably still use the module indirectly.
Anyway, getting rid of the module still seems useful -- we can
k...@freefriends.org (Karl Berry) writes:
FWIW, I also agree with just removing the module instead of trying to
ever-escalate warnings. My experience is that few people are likely to
deal with it until it becomes an error regardless of warning.
Alas, I don't think it becomes an error even if
.
Alas, I don't think it becomes an error even if we remove it -- I recall
that gnulib-tool just prints another warning for unknown modules. But
it shouldn't do any harm, which is the important aspect.
I have removed the module now.
Except that you forgot to remove 'exit' from
I noticed this warning in one of my projects (gsasl):
Notice from module exit:
This module is obsolete. It will be removed on 2011-01-01. Use 'stdlib'.
Time to remove the module?
/Simon
Simon Josefsson wrote:
I noticed this warning in one of my projects (gsasl):
Notice from module exit:
This module is obsolete. It will be removed on 2011-01-01. Use 'stdlib'.
Time to remove the module?
Well, if you were still using this module, that is, this notice did not catch
your
Bruno Haible br...@clisp.org writes:
Simon Josefsson wrote:
I noticed this warning in one of my projects (gsasl):
Notice from module exit:
This module is obsolete. It will be removed on 2011-01-01. Use 'stdlib'.
Time to remove the module?
Well, if you were still using this module,
Hi Simon,
It is easy to miss the message -- gnulib-tool's output is quite verbose.
Would it help if the user had to press enter to continue? That could be
a problem for automated builds, but someone is bound to notice the
problem eventually in that case though.
'gettextize' requires the
Bruno Haible br...@clisp.org writes:
Hi Simon,
It is easy to miss the message -- gnulib-tool's output is quite verbose.
Would it help if the user had to press enter to continue? That could be
a problem for automated builds, but someone is bound to notice the
problem eventually in that case
Hello,
* Bruno Haible wrote on Sun, May 01, 2011 at 09:38:43PM CEST:
Should we just play more with boldface output?
This sounds like an arms race again. Whenever that happens, it is
usually most helpful in the long to consider removing output, or
producing some of the other output more
Hello Simon,
* Simon Josefsson wrote on Sun, May 01, 2011 at 09:47:06PM CEST:
Bruno Haible br...@clisp.org writes:
'gettextize' requires the user to press Enter to acknowledge the output. And
it has annoyed a lot of people. Some distros patch out this part of
gettextize.
In summary,
Simon Josefsson wrote:
How about just removing the module? If something breaks, the maintainer
can track it down, and will notice that the module disappeared, and fix
the package.
OK. I won't object any more. Feel free to remove the module.
Bruno
--
In memoriam Itzhak Katzenelson
FWIW, I also agree with just removing the module instead of trying to
ever-escalate warnings. My experience is that few people are likely to
deal with it until it becomes an error regardless of warning.
I would agree even more with keeping the module as an alias for stdlib
so as to avoid this
13 matches
Mail list logo
