On Jul 6 02:01, Eric Blake wrote:
Should man/man1/sh.1 always belong to bash, or should I use readlink
to ensure that I am only upgrading that link if it was to ash? In other
words, for users smart enough to replace /bin/sh with zsh, are they
also going to want to replace the /bin/sh
Hi Maintainers of
neon
curl
exim
fetchmail
links
lynx
mutt
openssh
pine
postgresql
python
stunnel
uw-imap
wget
lftp
xemacs
openldap
lighttpd
clamav
GNOME
cyrus-sasl
w3m
I've just uploaded the brand new OpenSSL release 0.9.8. This release
is ABI
All,
I am putting together octave-forge as a companion package for octave, which
will require octave. Comments requested.
This companion package will have to be updated whenever octave is, as it uses
the octave abi, which is not stable. octave-forge is in Debian, which also has
a separate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 7/5/2005 9:21 PM:
2005-07-05 Eric Blake [EMAIL PROTECTED]
* templates/generic-build-script (options): Add almostall,
help, version.
(help, version): New functions.
(install): Support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Changes from 3.0-4:
+ provide man/man1/sh.1.gz - bash.1.gz
+ improve postinstall/preremove scripts per yesterday's discussions
I think this version is ready for primetime, so my setup.hint no longer
mentions a test version. You can delete 2.05b-16,
On Jul 6 07:12, Eric Blake wrote:
I think this version is ready for primetime, so my setup.hint no longer
mentions a test version. You can delete 2.05b-16, and 3.0-[34], leaving
2.05b-17 as previous and 3.0-5 as current. The following need to be done
with ash, then both packages uploaded
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 7/6/2005 7:29 AM:
+ remove /usr/share/man/man1/ash.1 from the package
^
you meant sh.1, don't you?
Oops, yes.
ln -f /bin/bash.exe /bin/sh.exe ||
On Wed, 6 Jul 2005, Eric Blake wrote:
According to Eric Blake on 7/5/2005 9:21 PM:
2005-07-05 Eric Blake ebb9atbyu.net
* templates/generic-build-script (options): Add almostall,
help, version.
(help, version): New functions.
(install): Support manifest lists.
On Jul 6 07:43, Eric Blake wrote:
Hmm - I missed that one, thinking I had already read it (but I did see the
one two minutes later about the man pages). Do you want to abort the mail
I sent to cygwin-announce, and let me try again with a -6 release? Or do
we just go with the -5 release
On Jul 6 03:19, James R. Phillips wrote:
Core Maintainers,
octave-2.1.71-1 packages are ready for uploading. These have a run-time
dependency on the recently uploaded lapack-3.0 package.
The issues Teun Burgers identified with the placement of doc files have been
fixed. Thanks, Teun.
Would it make sense to have Cygwin setup run the equivalent of the
following on install?
grep '^Mem:' /proc/meminfo | awk '{print $1}' | \
xargs -ri expr {} / 1048576 | \
xargs regtool -i set /HKLM/Software/Cygnus\ Solutions/Cygwin/heap_chunk_in_mb
Or should Cygwin determine and use the
--- Corinna Vinschen wrote:
Your setup.hint requires isn't quite what I'd expect. Rather than
just giving readline as dependency, which pulls in 2 versions of
libreadline and 2 versions of libncurses, could you please be more
specific and give the exact dependencies your package needs, as,
--- Corinna Vinschen wrote:
Your setup.hint requires isn't quite what I'd expect. Rather than
just giving readline as dependency, which pulls in 2 versions of
libreadline and 2 versions of libncurses, could you please be more
specific and give the exact dependencies your package needs, as,
Hm, well a first step would be identifying the correct version of libreadline,
since the ncurses libraries are libreadline dependencies.
But, short of deleting dlls, and checking to see if the program still loads,
I'm not sure how to do it.
cygcheck is your friend. cygcheck bash.exe, on
--- Eric Blake wrote:
cygcheck is your friend. cygcheck bash.exe, on bash-3.0-x for
example, explicitly lists cygreadline6.dll in the dependency list.
From there, cygcheck -f /bin/cygreadline6.dll outputs
libreadline6-5.0-2, confirming that it was indeed libreadline6.
Also, if you
On Wed, 6 Jul 2005, James R. Phillips wrote:
--- Corinna Vinschen wrote:
Your setup.hint requires isn't quite what I'd expect. Rather than
just giving readline as dependency, which pulls in 2 versions of
libreadline and 2 versions of libncurses, could you please be more
specific and
--- Igor Pechtchanski wrote:
In building the program, the gcc linker commands use the flag
-lreadline. Since both static and dynamic readline link libraries are
present in /lib, apparently the linker prefers the dynamic library,
ending in .dll.a. Is this a correct understanding of gcc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 7/6/2005 1:19 AM:
Looks basically good to me and I was going to use it for the 00ash.sh
script. It just doesn't work on NTFS. The reason is that, as soon as
the hardlink has been created, the script will fail to
--- Corinna Vinschen wrote:
Your setup.hint requires isn't quite what I'd expect. Rather than
just giving readline as dependency, which pulls in 2 versions of
libreadline and 2 versions of libncurses, could you please be more
specific and give the exact dependencies your package needs, as,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Let's try this again.
Changes from 3.0-5:
+ use cp, not ln, when creating /bin/sh
I think this version is ready for primetime, so my setup.hint no longer
mentions a test version. You can delete 2.05b-16, and 3.0-[345], leaving
2.05b-17 as previous
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now that bash is providing /bin/sh, the following packages need to revisit
their dependencies in setup.hint. Since both ash and bash are in Base,
not much will break if you don't do it immediately, but you might as well
match reality when you next
At 09:45 AM 7/6/2005 +0200, you wrote:
Hi Maintainers of
neon
curl
exim
fetchmail
links
lynx
mutt
openssh
pine
postgresql
python
stunnel
uw-imap
wget
lftp
xemacs
openldap
lighttpd
clamav
GNOME
cyrus-sasl
w3m
I've just uploaded the brand new OpenSSL
22 matches
Mail list logo
