On 7/28/2015 12:40 PM, Corinna Vinschen wrote:
On Jul 28 12:36, Ken Brown wrote:
On 7/28/2015 12:23 PM, Eric Blake wrote:
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware access
On 7/28/2015 12:23 PM, Eric Blake wrote:
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware access will be able to
post the !ready cookies all at the same time.
Corinna or Yaakov,
On 7/26/2015 1:55 PM, Achim Gratz wrote:
Ken Brown writes:
In that case there's probably no reason for me to wait, unless Achim
wants more time for maxima. Achim, what's your preference? If you
want, you can install the new clisp from my repository
(http://sanibeltranquility.com/cygwin
On 7/22/2015 8:57 PM, Alexey Sokolov wrote:
23.07.2015 00:03, David Stacey :
cygport ./znc.cygport prep compile
Nothing out of the ordinary there. This gives the following error:
configure.ac:255: Something is trying to use the C compiler. Since
this is a C++ project, this should
On 7/23/2015 5:04 PM, Alexey Sokolov wrote:
23.07.2015 21:49, Alexey Sokolov пишет:
23.07.2015 14:24, Ken Brown пишет:
On 7/22/2015 8:57 PM, Alexey Sokolov wrote:
23.07.2015 00:03, David Stacey :
cygport ./znc.cygport prep compile
Nothing out of the ordinary there. This gives
On 7/22/2015 4:16 AM, Corinna Vinschen wrote:
On Jul 21 16:47, Ken Brown wrote:
On 7/21/2015 4:25 PM, Achim Gratz wrote:
Ken Brown writes:
I've rebuilt clisp on both 32-bit and 64-bit, now using libsigsegv on
64-bit, and I don't see any regressions. In particular, it passes the
test suite
On 7/20/2015 9:03 AM, Ken Brown wrote:
On 7/20/2015 7:20 AM, Corinna Vinschen wrote:
I uploaded snapshots as well as a 2.2.0-0.1 test release. Please
give it a try.
Everything is fine as far as emacs is concerned. I'll rebuild clisp and
test it later today.
I've rebuilt clisp on both 32
On 7/21/2015 4:25 PM, Achim Gratz wrote:
Ken Brown writes:
I've rebuilt clisp on both 32-bit and 64-bit, now using libsigsegv on
64-bit, and I don't see any regressions. In particular, it passes the
test suite. I don't know enough about clisp to test it further.
Does maxima still work
On 7/20/2015 7:20 AM, Corinna Vinschen wrote:
On Jul 19 10:37, Corinna Vinschen wrote:
On Jul 18 14:41, Eric Blake wrote:
On 07/18/2015 02:11 PM, Corinna Vinschen wrote:
OTOH, calling certain Cygwin functions might require lots of stack.
E.g. open/read/write/close requires more than 2K stack,
applications would need to be rebuilt? I see:
diffutils [me]
m4 [me]
clisp [Ken Brown]
I was planning to rebuild 64-bit clisp anyway, to take advantage of the
new libsigsegv, so I can rebuild on 32-bit also. But there's no big
rush, so I'll probably wait for Cygwin 2.2.0 unless someone reports
On 7/17/2015 3:32 AM, Corinna Vinschen wrote:
On Jul 15 16:12, Ken Brown wrote:
On 7/15/2015 2:28 PM, Corinna Vinschen wrote:
On Jul 15 16:24, Marco Atzeri wrote:
Dear All,
I spent a bit of time checking the real situation of the packages
still missing as 64 bit port.
After xdelta, bsdiff
On 7/15/2015 2:28 PM, Corinna Vinschen wrote:
On Jul 15 16:24, Marco Atzeri wrote:
Dear All,
I spent a bit of time checking the real situation of the packages
still missing as 64 bit port.
After xdelta, bsdiff and iperf porting, without counting the few mingw ones,
the duplicates we are down to
On 7/15/2015 1:34 AM, Achim Gratz wrote:
Ken Brown writes:
On 7/14/2015 3:51 PM, Achim Gratz wrote:
biber
This all set and uploaded to my release area.
Thanks. Just to be sure, this build uses the system supplied Unicode
modules or did you fatpack them? I've downgraded Unicode-Normalize
On 7/14/2015 3:51 PM, Achim Gratz wrote:
These packages place module files into vendor_perl while the package
name has nothing to do with Perl (not all of them are available for both
architectures):
biber
This all set and uploaded to my release area. I'll just have to either change
the
On 5/25/2015 2:45 PM, Ken Brown wrote:
BTW, I contacted Philip Kime, the author of Biber, about
Unicode::Normalize. He told me that version 1.18 is unusably slow.
Here's a bug report he filed about it:
https://rt.cpan.org/Public/Bug/Display.html?id=102766
I think he's planning to pursue
On 7/10/2015 3:33 PM, Yaakov Selkowitz wrote:
On Fri, 2015-07-10 at 14:30 -0400, Ken Brown wrote:
On 5/25/2015 2:45 PM, Ken Brown wrote:
BTW, I contacted Philip Kime, the author of Biber, about
Unicode::Normalize. He told me that version 1.18 is unusably slow.
Here's a bug report he filed
On 7/5/2015 2:02 AM, Achim Gratz wrote:
David Rothenberger writes:
I've rebuilt the package as curr and not test and uploaded to my area. I
did not create the !ready file.
Is this the right way to do this? Or should I release a test package?
As long as you remember what you did it's going to
On 7/5/2015 2:31 PM, Yaakov Selkowitz wrote:
On Sun, 2015-07-05 at 09:26 -0400, Ken Brown wrote:
On 7/5/2015 2:02 AM, Achim Gratz wrote:
David Rothenberger writes:
I've rebuilt the package as curr and not test and uploaded to my area. I
did not create the !ready file.
Is this the right way
According to the documentation of SSH_KEY, You'll need to set this if
your private key isn't already loaded into a running ssh-agent(1), and
it doesn't have one of the expected file names such as ~/.ssh/id_rsa.
But I don't see in the source that cygport checks for one of the
expected file
On 6/27/2015 3:18 PM, Andrew Schulman wrote:
According to the documentation of SSH_KEY, You'll need to set this if
your private key isn't already loaded into a running ssh-agent(1), and
it doesn't have one of the expected file names such as ~/.ssh/id_rsa.
But I don't see in the source that
On 6/16/2015 7:52 PM, Yaakov Selkowitz wrote:
On Tue, 2015-06-16 at 10:24 -0400, Ken Brown wrote:
The syntax for 'fmtutil' has changed in TeX Live 2015. The attached
patch accommodates that change.
Just curious, what changed? AFAICS the fmtutil-sys in 20140523-2 also
accepts --byfmt
On 5/28/2015 2:14 PM, Yaakov Selkowitz wrote:
Ken,
See $SUBJECT. emacs-auctex's copy is in texmf-site and texlive's is in
texmf-dist, so while they don't physically clobber each other I suspect
we only want one of them; I'm just not sure which.
I agree. I think emacs-auctex should be the
On 5/28/2015 2:15 PM, Yaakov Selkowitz wrote:
Ken,
An insecure usage of /tmp has been reported in mktexlsr:
https://bugzilla.redhat.com/show_bug.cgi?id=1181167
http://pkgs.fedoraproject.org/cgit/texlive.git/plain/texlive-bz979176.patch
Thanks for the heads-up. I'm on vacation, but I'll look
On 5/25/2015 3:00 AM, Achim Gratz wrote:
Ken Brown writes:
The latest version of Biber requires autovivification, XML::Writer,
and Text::Roman. And Test::Difference is required for running the
tests. Can you add those?
I have the first two already from my last look at Biber… OK, the rest
On 5/25/2015 9:12 AM, Ken Brown wrote:
On 5/25/2015 3:00 AM, Achim Gratz wrote:
I don't know if it's still possible to build on 5.22, depending on where
in the deprecation cycle we are with that function. But the earlier
module versions have been pulled from CPAN anyway and only 1.18
On 5/25/2015 2:31 PM, Achim Gratz wrote:
Ken Brown writes:
biber-1.8 seems fine with perl-5.22.0. Since I may be out of town
with poor internet access when you're ready for the transition, I went
ahead and uploaded it to sourceware (x86_64 only), along with a new
release of texlive-collection
On 5/24/2015 4:02 PM, Achim Gratz wrote:
I've built perl-5.22.0-RC2 and bootstrapped the Perl distributions for
Cygwin (well, most of them -- I will send another ITA for some
additional ones I've hat to build later). It doesn't make much sense to
try a test release on sourceware, so I've
On 5/20/2015 3:39 PM, Achim Gratz wrote:
Ken Brown writes:
I'm wondering what your plans are for Perl 5.22, which I think is due
to be released in a couple weeks.
I've just built perl-5.33-RC1. I need to do some changes to actually be
able to package the result and then of course install
On 5/8/2015 7:16 PM, Yaakov Selkowitz wrote:
On Wed, 2015-05-06 at 14:33 -0400, Ken Brown wrote:
Now that we've moved from cygwin-1.7.x to cygwin-2.x.y, line 681 of
pkg_pkg.cygpart no longer filters out cygwin. Presumably you just
want to replace cygwin-1 by cygwin-2, unless there's a reason
Now that we've moved from cygwin-1.7.x to cygwin-2.x.y, line 681 of
pkg_pkg.cygpart no longer filters out cygwin. Presumably you just
want to replace cygwin-1 by cygwin-2, unless there's a reason to
allow for the possibility that maintainers are building without having
the latest version of
Hi Achim,
I'm wondering what your plans are for Perl 5.22, which I think is due to
be released in a couple weeks. I'm expecting to release TeX Live 2015
in mid June, and it would be nice to be able to update Biber to the
current version at the same time.
Do you think you will have released
On 3/23/2015 2:45 AM, Achim Gratz wrote:
As I said, I've revoked the maxima-exec-clisp package for now, so
whether you either come up with a solution for that problem or conclude
that dumping of executables isn't going to be supported on Cygwin, I'm
fine.
OK, that's good. I'd still like to
On 3/22/2015 4:50 PM, Achim Gratz wrote:
Ken Brown writes:
And indeed it does. I've still got a couple of things to clean up,
but I expect to upload a new clisp soon that no longer uses lisp.dll.
I hope that will solve the Maxima problem
It doesn't… Instead of lisp.dll it now requires
On 3/22/2015 6:33 PM, Ken Brown wrote:
On 3/22/2015 4:50 PM, Achim Gratz wrote:
Ken Brown writes:
And indeed it does. I've still got a couple of things to clean up,
but I expect to upload a new clisp soon that no longer uses lisp.dll.
I hope that will solve the Maxima problem
It doesn't
On 3/17/2015 9:47 PM, Yaakov Selkowitz wrote:
A .def file can be used for two purposes:
1) to specify which symbols to export in a DLL/EXE, in place of
dllexport or -Wl,--export-all-symbols (EXPORTS)
2) to resolve symbols by declaring them in other DLL/EXE(s), in place of
a .dll.a (IMPORTS)
On 3/17/2015 3:20 PM, Achim Gratz wrote:
Ken Brown writes:
Great. Thanks for testing. There's probably no reason for me to
upload a new clisp package right now (unless it would help you). But
I'll give you a heads up when I'm ready to do that.
I've now drilled to the bottom of what I had
On 3/17/2015 8:17 PM, Jon TURNEY wrote:
On 17/03/2015 22:40, Ken Brown wrote:
Yes. But that makes me wonder if I made things too complicated and
could have avoided building lisp.dll. The native Windows build of clisp
creates a lisp.def file, containing the symbols of lisp.exe, and it just
On 3/17/2015 8:54 PM, Ken Brown wrote:
On 3/17/2015 8:17 PM, Jon TURNEY wrote:
On 17/03/2015 22:40, Ken Brown wrote:
Yes. But that makes me wonder if I made things too complicated and
could have avoided building lisp.dll. The native Windows build of clisp
creates a lisp.def file, containing
On 3/17/2015 5:40 PM, Yaakov Selkowitz wrote:
On Tue, 2015-03-17 at 17:15 -0400, Ken Brown wrote:
On 3/17/2015 3:20 PM, Achim Gratz wrote:
Ken Brown writes:
Great. Thanks for testing. There's probably no reason for me to
upload a new clisp package right now (unless it would help you
On 3/16/2015 4:07 PM, Achim Gratz wrote:
Yaakov Selkowitz writes:
Is there an issue with stripping clisp executables?
Yes, with the executable dumps.
Is there a magic
number we can use to detect these automatically?
File identifies them as plain executables. CLisp knows which runtime
On 3/16/2015 3:41 PM, Achim Gratz wrote:
Achim Gratz writes:
The loading of memory images via clisp works, so I'll pull the
maxima-exec-clisp package until we get to the bottom of this.
Hmm. Scratch that, I think I got the maxima.exe (dumped image) to work.
Let's see if it survives
On 3/15/2015 12:40 PM, Achim Gratz wrote:
Ken Brown writes:
My work was based on the tip of the upstream Mercurial repository,
which shows a version number of 2.49+ and is at revision 15623. So I
was thinking of using 2.49+hg15623 as the version number. Will upset
be happy
On 3/15/2015 2:19 PM, Yaakov Selkowitz wrote:
On Sun, 2015-03-15 at 13:37 -0400, Ken Brown wrote:
This sounds like a packaging error on my part. First of all, lisp.dll
is new with the latest clisp; it was part of my solution to the dynamic
loading problem. But from what you say, it sounds
On 3/15/2015 3:14 PM, Achim Gratz wrote:
Ken Brown writes:
I think my new proposal (with /usr/bin/cyglisp.dll and
/usr/lib/liblisp.dll.a) will work better. I don't know whether it's
best to split off libclisp and clisp-devel subpackages. Fedora has a
separate clisp-devel package
On 3/12/2015 7:00 PM, Achim Gratz wrote:
Achim Gratz writes:
Ken, would you still know if the Log-Log4Perl and Text-BibTeX tests were
clean previously? I'm getting what looks like an encoding problem from
Text-BibTeX and an offset in some file sizes(?) for Log-Log4Perl.
No, sorry. I don't
On 3/12/2015 2:43 AM, Achim Gratz wrote:
Yaakov Selkowitz writes:
My work was based on the tip of the upstream Mercurial repository, which
shows a version number of 2.49+ and is at revision 15623. So I was
thinking of using 2.49+hg15623 as the version number. Will upset be
happy with that?
On 3/12/2015 2:52 AM, Achim Gratz wrote:
To the maintainers of other Perl distributions: if there's any you want
to part with, please let me know and I'll most likely adopt them.
Please take all of mine.
Thanks.
Ken
On 3/11/2015 6:20 PM, Yaakov Selkowitz wrote:
On Wed, 2015-03-11 at 17:35 -0400, Ken Brown wrote:
I've succeeded in making dynamic loading of modules work in clisp on
Cygwin, and I'll be issuing a new release soon.
Yeah!
My work was based on the tip of the upstream Mercurial repository
I've succeeded in making dynamic loading of modules work in clisp on
Cygwin, and I'll be issuing a new release soon.
My work was based on the tip of the upstream Mercurial repository, which
shows a version number of 2.49+ and is at revision 15623. So I was
thinking of using 2.49+hg15623 as
Reini,
Do you plan to resume development of the gdi module? If not, I think
clisp-gdi will have to be dropped from the distribution the next time
there's a new release of clisp. gdi no longer compiles with the current
clisp development trunk, and I don't have the interest or the expertise
This is needed for the upcoming clisp-2.49. [*]
D=http://sanibeltranquility.com/cygwin/x86/release/svm
wget -x -nH --cut-dirs=1 \
${D}/svm-3.20-1-src.tar.xz \
${D}/svm-3.20-1.tar.xz \
${D}/setup.hint \
${D}/svm-debuginfo/svm-debuginfo-3.20-1.tar.xz \
${D}/svm-debuginfo/setup.hint \
On 2/21/2015 7:59 AM, Reini Urban wrote:
On 02/21/2015 04:44 AM, Ken Brown wrote:
On 2/19/2015 2:46 PM, Reini Urban wrote:
And the deal with the latest clisp 2.49 was that modules can be
dynaloaded.
If the gnulib steps would work. I never did for me. And I fixed most of
the other
module
On 2/21/2015 5:03 AM, David Billinghurst wrote:
On 20/02/2015 9:30 AM, Ken Brown wrote:
In that case, I think I'll go ahead and release what I have and see if it's of
use to anyone.
Ken
I have built and tested maxima-5.43.1 with your clisp release on cygwin64.
Perfect test results.I
On 2/19/2015 2:46 PM, Reini Urban wrote:
And the deal with the latest clisp 2.49 was that modules can be dynaloaded.
If the gnulib steps would work. I never did for me. And I fixed most of
the other
module compilation problems before.
But I just discovered that clisp-2.49 builds fine with the
On 2/19/2015 12:44 PM, Corinna Vinschen wrote:
On Feb 19 12:19, Ken Brown wrote:
On 2/19/2015 11:46 AM, Ken Brown wrote:
On 2/19/2015 10:43 AM, Reini Urban wrote:
On 02/19/2015 10:38 AM, Corinna Vinschen wrote:
On Feb 18 17:41, Ken Brown wrote:
Help with basic x86_64 assembler is ok, I did
On 2/19/2015 2:46 PM, Reini Urban wrote:
On 02/19/2015 06:19 PM, Ken Brown wrote:
On 2/19/2015 11:46 AM, Ken Brown wrote:
On 2/19/2015 10:43 AM, Reini Urban wrote:
On 02/19/2015 10:38 AM, Corinna Vinschen wrote:
On Feb 18 17:41, Ken Brown wrote:
Help with basic x86_64 assembler is ok, I did
On 2/19/2015 10:43 AM, Reini Urban wrote:
On 02/19/2015 10:38 AM, Corinna Vinschen wrote:
On Feb 18 17:41, Ken Brown wrote:
Help with basic x86_64 assembler is ok, I did it for Cygwin with help
from Kai Tietz.
The main difference to Linux you have to look out for is the different
calling
On 2/19/2015 11:46 AM, Ken Brown wrote:
On 2/19/2015 10:43 AM, Reini Urban wrote:
On 02/19/2015 10:38 AM, Corinna Vinschen wrote:
On Feb 18 17:41, Ken Brown wrote:
Help with basic x86_64 assembler is ok, I did it for Cygwin with help
from Kai Tietz.
The main difference to Linux you have
I've been trying to adopt Reini's packages that have not yet been ported to
64-bit Cygwin and that have some connection to packages I already maintain. The
next one on my list is ffcall.
Unfortunately, the source has a lot of assembler code in it, so I will almost
certainly need help from
On 2/18/2015 3:08 PM, Corinna Vinschen wrote:
On Feb 18 13:28, Yaakov Selkowitz wrote:
On Wed, 2015-02-18 at 13:49 -0500, Ken Brown wrote:
I've been trying to adopt Reini's packages that have not yet been ported to
64-bit Cygwin and that have some connection to packages I already maintain
On 2/18/2015 2:28 PM, Yaakov Selkowitz wrote:
On Wed, 2015-02-18 at 13:49 -0500, Ken Brown wrote:
I've been trying to adopt Reini's packages that have not yet been ported to
64-bit Cygwin and that have some connection to packages I already maintain. The
next one on my list is ffcall.
I'm
The x86 build is the same as Reini's build of 2.4.0-2, except for (a) a
tweak to allow it to build with the current gcc and (b) a minor
packaging change: The package provides some example C/C++ files in
/usr/share/doc/fcgi/examples, and the build process compiles these.
Reini put the
This builds easily on both arches, using essentially the same cygport
file as Yaakov used for icu-51.2-1 on x86_64. I tested it by rebuilding
the TeX Live binaries against libicu54.
D=http://sanibeltranquility.com/cygwin/x86/release/icu
wget -x -nH --cut-dirs=1 \
${D}/icu-54.1-1-src.tar.xz \
On 2/10/2015 11:14 PM, Yaakov Selkowitz wrote:
clispORPHANED (Reini Urban)
As I mentioned in the libopenssl098 thread, I have a build of clisp-2.48
(32-bit only for now) that seems to work and that links against current versions
of all libraries.
On 2/11/2015 11:10 PM, Ken Brown wrote:
On 2/11/2015 7:50 PM, Yaakov Selkowitz wrote:
On Thu, 2015-01-15 at 16:46 -0500, Ken Brown wrote:
On 1/5/2015 12:52 PM, Achim Gratz wrote:
Ken Brown writes:
Do you have an opinion about that? I suggested /etc/texmf/postinstall
or /var/lib/texmf
On 2/11/2015 7:50 PM, Yaakov Selkowitz wrote:
On Thu, 2015-01-15 at 16:46 -0500, Ken Brown wrote:
On 1/5/2015 12:52 PM, Achim Gratz wrote:
Ken Brown writes:
Do you have an opinion about that? I suggested /etc/texmf/postinstall
or /var/lib/texmf/postinstall, but Achim had other ideas
On 2/3/2015 4:17 AM, Corinna Vinschen wrote:
On Feb 2 10:46, Ken Brown wrote:
I've now begun working on the 64-bit build. I found a few minor things I
had to change, and the build was pretty far along, when I apparently hit a
gcc bug:
[...]
Oh, that's too bad. I hope somebody from the gcc
On 2/3/2015 6:33 AM, Corinna Vinschen wrote:
Hey guys,
On Jan 28 21:23, Corinna Vinschen wrote:
https://cygwin.com/setup-test-x86.exe
https://cygwin.com/setup-test-x86_64.exe
These should fix the aforementioned bug I introduced, as well as another
subtil problem when checking and
On 2/3/2015 10:27 AM, Corinna Vinschen wrote:
On Feb 3 08:04, Ken Brown wrote:
On 2/3/2015 6:33 AM, Corinna Vinschen wrote:
Hey guys,
On Jan 28 21:23, Corinna Vinschen wrote:
https://cygwin.com/setup-test-x86.exe
https://cygwin.com/setup-test-x86_64.exe
These should fix
On 1/30/2015 11:40 AM, Ken Brown wrote:
On 1/30/2015 8:25 AM, Ken Brown wrote:
On 1/30/2015 4:41 AM, Corinna Vinschen wrote:
On Jan 29 15:25, Ken Brown wrote:
I'm attaching the patches that I applied (on top of Reini's patches) in
order to make the build succeed. I also had to use libdb4.5
On 1/30/2015 8:25 AM, Ken Brown wrote:
On 1/30/2015 4:41 AM, Corinna Vinschen wrote:
On Jan 29 15:25, Ken Brown wrote:
I'm attaching the patches that I applied (on top of Reini's patches) in
order to make the build succeed. I also had to use libdb4.5 instead of
libdb4.8.
Is that ok? I mean
On 1/30/2015 2:02 PM, Yaakov Selkowitz wrote:
On Fri, 2015-01-30 at 11:40 -0500, Ken Brown wrote:
On 1/30/2015 8:25 AM, Ken Brown wrote:
On 1/30/2015 4:41 AM, Corinna Vinschen wrote:
On Jan 29 15:25, Ken Brown wrote:
I'm attaching the patches that I applied (on top of Reini's patches
On 1/30/2015 4:41 AM, Corinna Vinschen wrote:
Hi Ken,
On Jan 29 15:25, Ken Brown wrote:
On 1/23/2015 8:48 AM, Ken Brown wrote:
My guess is correct. lisp.exe uses bit 31 (counting from the LSB) as a marker
during garbage collection, and this is incompatible with Cygwin's use of high
memory
On 1/23/2015 8:48 AM, Ken Brown wrote:
My guess is correct. lisp.exe uses bit 31 (counting from the LSB) as a marker
during garbage collection, and this is incompatible with Cygwin's use of high
memory for the heap. I think I know how to fix this (by defining
LINUX_NOEXEC_HEAPCODES
On 1/23/2015 3:09 PM, Corinna Vinschen wrote:
Hi Ken,
On Jan 23 08:48, Ken Brown wrote:
On 1/14/2015 4:19 PM, Ken Brown wrote:
It is. There's a configure option --ignore-absence-of-libsigsegv. But there
are more serious problems, affecting both the 32-bit and 64-bit versions. (So
even just
On 1/23/2015 5:57 AM, Dr. Volker Zell wrote:
gcc -c -ggdb -O2 -pipe -Wimplicit-function-declaration
-fdebug-prefix-map=/cygdrive/d/misc/src/release/xemacs-21.4.22-2.i686/build=/usr/src/debug/xemacs-21.4.22-2
On 1/14/2015 4:19 PM, Ken Brown wrote:
On 1/14/2015 12:46 PM, Achim Gratz wrote:
Corinna Vinschen writes:
Clisp is not yet ported to 64bit and it has problems under 32bit as well
(temporary file generation) that also affect Maxima from ports.
If it's a problem with the Cygwin DLL, it would
On 1/5/2015 12:52 PM, Achim Gratz wrote:
Ken Brown writes:
Do you have an opinion about that? I suggested /etc/texmf/postinstall
or /var/lib/texmf/postinstall, but Achim had other ideas. The only
precedent we have so far is Achim's new _autorebase, which uses
/etc/rebase.
Even for this I
On 1/14/2015 12:46 PM, Achim Gratz wrote:
Corinna Vinschen writes:
Clisp is not yet ported to 64bit and it has problems under 32bit as well
(temporary file generation) that also affect Maxima from ports.
If it's a problem with the Cygwin DLL, it would be nice to get a
bug report and,
On 1/5/2015 2:51 AM, Yaakov Selkowitz wrote:
On 2014-12-18 07:11, Ken Brown wrote:
On 12/18/2014 3:22 AM, Achim Gratz wrote:
Ken Brown writes:
+if [ -d /usr/share/texmf-dist ]
Looks like you'd want
if [ -d ${D}/usr/share/texmf-dist ]
here.
Thanks. I hope this is the last
On 12/18/2014 3:22 AM, Achim Gratz wrote:
Ken Brown writes:
+ if [ -d /usr/share/texmf-dist ]
Looks like you'd want
if [ -d ${D}/usr/share/texmf-dist ]
here.
Thanks. I hope this is the last of the careless mistakes.
In postinstall scripts we remove the updmap calls
On 12/17/2014 4:52 AM, Corinna Vinschen wrote:
On Dec 17 10:39, Corinna Vinschen wrote:
On Dec 16 16:11, Ken Brown wrote:
On 12/16/2014 8:23 AM, Corinna Vinschen wrote:
What would be most helpful is to get a piece of documentation for us
maintainers how to use the new _autorebase facility
On 12/16/2014 6:08 PM, Ken Brown wrote:
Sorry, there was a stupid mistake in one of the patches. The corrected
one is attached.
This is embarrassing, but there was a mistake in a second patch also.
I'm reattaching the complete set of cygport patches, corrected.
I had made some minor
On 12/16/2014 8:23 AM, Corinna Vinschen wrote:
What would be most helpful is to get a piece of documentation for us
maintainers how to use the new _autorebase facility, sent with a fat
HEADSUP subject, and which we can ideally add to setup.html.
More importantly, maintainers need to be told
${postinstalldir}/texlive.refresh_fmts ]
then
/usr/bin/fmtutil-sys --refresh
mv -f ${postinstalldir}/texlive.refresh_fmts \
${postinstalldir}/texlive.refresh_fmts.done
fi
From 408d371b734ab7295adfaf1d1ad9e4fa9481ce7c Mon Sep 17 00:00:00 2001
From: Ken Brown kbr...@cornell.edu
Date: Tue, 25 Nov 2014
On 12/16/2014 5:49 PM, Ken Brown wrote:
Now that setup.exe supports perpetual postinstall scripts, I'd like to
streamline the TeX Live postinstall process. I'm attaching two perpetual
postinstall scripts that I'd like to use (one before the ordinary postinstall
scripts and one after), as well
On 12/14/2014 3:56 AM, Achim Gratz wrote:
Packages rebuilt with cygport including the changes discussed with Ken
and pre-compiled setup.exe files added.
--8---cut here---start-8---
cygwin=http://cygwin.stromeko.net/
wget
On 12/14/2014 12:52 PM, Achim Gratz wrote:
Ken Brown writes:
I just noticed a couple of things about the base address. First, you
have a typo in line 4 of rebaselst (missing 'd').
I'll fix that before the actual release. Unless someone defines
BaseAddress in the environment this doesn't
On 12/14/2014 3:48 PM, Achim Gratz wrote:
Ken Brown writes:
The changes look good, and it works fine on an existing installation.
But there's a problem with a new installation. The autorebase
postinstall script seems to hang in one of the calls to find, which
I finally killed through the Task
On 12/13/2014 10:56 AM, Achim Gratz wrote:
--8---cut here---start-8---
wget=wget -rxnH http://cygwin.stromeko.net/noarch/release;
$wget/_autorebase-001000-1-src.tar.xz
$wget/_autorebase-001000-1.tar.xz
$wget/setup.hint
--8---cut
On 12/13/2014 10:56 AM, Achim Gratz wrote:
Requirements before deployment:
- all autodep stuff referring to _autorebase must be removed
- setup.exe version 2.858 or later must be used
Notes:
There will be no ITP for _incautorebase since Corinna wanted a
replacement for _autorebase instead.
On 12/9/2014 5:43 AM, Corinna Vinschen wrote:
On Dec 8 15:52, Ken Brown wrote:
On 12/8/2014 11:48 AM, Achim Gratz wrote:
Ken Brown writes:
I'm not convinced that we need to worry so much about all these
details. What if we just check (based on timestamps of files in
/etc/setup/*.lst.gz
On 12/9/2014 12:48 PM, Corinna Vinschen wrote:
On Dec 9 17:35, Achim Gratz wrote:
Corinna Vinschen writes:
I still don't grok why everybody is so hot on keeping the base install
so very small. Our Base package set is really tiny in comparison
with any Linux distro. Perl is default on most
On 12/9/2014 2:52 PM, Corinna Vinschen wrote:
On Dec 9 14:10, Ken Brown wrote:
On 12/9/2014 12:48 PM, Corinna Vinschen wrote:
Come to think of it. When exactly do we want to allow installing
packages without also installing the deps? How much sense does
this option really have?
I've had
On 12/7/2014 6:36 AM, Corinna Vinschen wrote:
On Dec 7 11:45, Achim Gratz wrote:
Corinna Vinschen writes:
The _update-info-dir script just collects all info files from /usr/info
and /usr/share/info and creates new dir using install-info. I was
hoping that the method from _{inc}autorebase
On 12/8/2014 11:48 AM, Achim Gratz wrote:
Ken Brown writes:
I'm not convinced that we need to worry so much about all these
details. What if we just check (based on timestamps of files in
/etc/setup/*.lst.gz) whether anything has been installed into
/usr/info or /usr/share/info since we last
On 12/6/2014 11:57 AM, Corinna Vinschen wrote:
Hi,
isn't it rather annoying that even Base packages have dependencies
outside the Base category? So, even if I perform a plain Base-only
installation, I get asked if dependencies shall be fullfilled, which, as
a question, is more than borderline
On 12/6/2014 12:57 PM, Corinna Vinschen wrote:
On Dec 6 12:40, Ken Brown wrote:
On 12/6/2014 11:57 AM, Corinna Vinschen wrote:
Hi,
isn't it rather annoying that even Base packages have dependencies
outside the Base category? So, even if I perform a plain Base-only
installation, I get asked
On 12/1/2014 3:16 PM, Achim Gratz wrote:
Achim Gratz writes:
This is now in Git together with the other corrections, but I haven't
tested it yet.
Needed two const qualifiers to compile on Cygwin and sorting is now
tested to work correctly. Please give it a spin, I'll be AFK until the
On 12/2/2014 3:57 PM, Corinna Vinschen wrote:
On Dec 2 21:50, Corinna Vinschen wrote:
On Nov 28 22:53, Achim Gratz wrote:
New versions of the setup programs and incremental autorebase package
are uploaded, plus my original texlive postinstall (not modified for the
new setup) for Ken to look
601 - 700 of 1041 matches
Mail list logo
