- Original Message -
From: David A. Cobb [EMAIL PROTECTED]
I've thought about suggesting the same thing but the problem with
that
scenario is that if you cancel an installation, then all sorts of
stuff
is uninstalled -- which probably isn't what you expected.
Probably not. But
Charles Wilson wrote:
Since gettext comes before libintl0, the uninstall/reinstall occured
in the proper order, and I still had a working system. Unlike ncurses,
alphabetization works for us here -- it would be bad if libintl0 was
installed (replacing cygintl.dll with the new version),
Gerrit P. Haase wrote:
What is the problem here? libintl and libintl1 are two different packages
with different names.
But there's only one nano. (sounds like an ad campaign) So, nano's
setup.hint has a line like:
requires: foo bar libintl
Later, the (then-)current nano will
Okay, I've uploaded and announced the new gettext packages:
gettext-0.10.40-1
libintl1-0.10.40-1
libintl-0.10.38-3
I also updated the setup.hint files on the server for the following
packages:
wget mutt nano vim sharutils
The maintainers of those packages should make a note
Okay, I've uploaded and announced the new gettext packages:
gettext-0.10.40-1
libintl1-0.10.40-1
libintl-0.10.38-3
I also updated the setup.hint files on the server for the following
packages:
wget mutt nano vim sharutils
The maintainers of those packages should make a note
I'd recommend specifying both, for users who click 'prev'.
If you don't list a prev version (implicitly or explicitly) then you
don't need both.
Rob
-Original Message-
From: Charles Wilson [mailto:[EMAIL PROTECTED]]
Right. But the one package could provide the same .dll
twice (until all
dependent packages are rebuilt).
I'd prefer not to complicate the libfooX package by
starting down the
path where libfoo1 contains both
- Original Message -
From: Charles Wilson [EMAIL PROTECTED]
Ouch. Do you know why it's not compatible? (i.e. is auto-import
breaking
something?)
Well, whaddaya know. I replaced my cygintl.dll with cygintl-1.dll and
wget/uuencode/etc still worked. I just assumed because I changed
- Original Message -
From: Charles Wilson [EMAIL PROTECTED]
The term glutton for punishment springs to mind.
:]
I think we should consider it the responsibility of the package
maintainer
to maintain all occurrences of the name of his package. So, it
would
be within your right
