Hi,
Can someone with the suitable powers reconfigure
http://sourceware.org/bugzilla/ so that I'm no longer the default
assignee for setup.exe bugs?
Thanks,
Max.
signature.asc
Description: OpenPGP digital signature
Dave Korn wrote:
Max Bowsher wrote on 02 May 2008 02:45:
Warren Young wrote:
Dave Korn wrote:
requires: cygwin libpng12
The requires: line looks wrong to meWhy libpng?
Ask Max. :)
Last time I looked there was a copy of libpng embedded in the doxygen
source tree. Building another
Warren Young wrote:
Dave Korn wrote:
requires: cygwin libpng12
The requires: line looks wrong to meWhy libpng?
Ask Max. :)
Last time I looked there was a copy of libpng embedded in the doxygen
source tree. Building another copy seemed rather dumb when it's in the
distro as a shared
Warren Young wrote:
Then other
package maintainers can rebuild for libexpat1 at their leisure. Unless,
that is, it's a big deal to port to expat 2?
I believe it's merely a matter of rebuilding.
Max.
signature.asc
Description: OpenPGP digital signature
Warren Young wrote:
Max Bowsher wrote:
* doxygen
I'm interested, contingent on seeing what it takes to build it.
It's a most bizarre and quirky buildsystem that I've never seen any
other package use.
* expat
I can do this one, but I'm concerned because expat.sf.net isn't
responding
Dave Korn wrote:
Oooh, only just noticed this one:
subversion 1.4.5-2OK
requires: cygwin libaprutil1 libapr1 libdb4.2 libneon26 expat libintl8
The requires: line is wrong. That should say libexpat0, which contains
the library DLL, not expat, which is the main
Greetings all,
I've been using Linux exclusively at work for over a year. Today I've
started dual-booting my primary machine to Linux too. I'm no longer
going to be using Windows on a daily basis, so I don't think I'll be
able to do an adequate job of package maintenance in the future.
Max Bowsher wrote:
Max Bowsher wrote:
SQLite is a small C library that implements a self-contained,
embeddable, zero-configuration SQL database engine.
...
Updated to 3.3.17-1.
The 3.3.14-0.1 packages were GTGed, so I'll upload in a few days if no
one says differently.
Uh, a few days
Max Bowsher wrote:
SQLite is a small C library that implements a self-contained,
embeddable, zero-configuration SQL database engine.
It will be a mandatory dependency of future Subversion releases.
http://mps.sh.nu/~maxb/cygsqlite3/release/sqlite3/
# sqlite3
sdesc: Embeddable SQL
Yaakov (Cygwin Ports) wrote:
Brian Dessent wrote:
If you configure setup with --enable-inilint it should build the inilint
tool as a standalone app. I don't know if it has bitrotted to pieces or
not.
That's good to know. But trying to build inilint in the current
snapshot sources leads
Yaakov (Cygwin Ports) wrote:
Max Bowsher wrote:
Well, I got it to compile again, but I couldn't get it to link. It
seems that the setup classes have become interdependent to the point at
which it's no longer possible to call the parser standalone from the
rest of setup any more.
I came
Lapo Luchini wrote:
Max Bowsher wrote:
SQLite is a small C library that implements a self-contained,
embeddable, zero-configuration SQL database engine.
Are you using Mingw or Cygwin file locking? (by default CYGWIN
includes Win32 in SQLite sources)
I had tried packaging it some time ago
A long long time ago, I said I'd adopt expat. I've finally got around to
finalizing packages:
http://mps.sh.nu/~maxb/cygexpat/release/expat/
I'm not sure whether I need a GTG review for this, so I'm posting anyway
to be on the safe side.
This is a re-release of the same upstream version as we
SQLite is a small C library that implements a self-contained,
embeddable, zero-configuration SQL database engine.
It will be a mandatory dependency of future Subversion releases.
http://mps.sh.nu/~maxb/cygsqlite3/release/sqlite3/
# sqlite3
sdesc: Embeddable SQL database engine
ldesc: SQLite is
The Python extension _ssl.dll currently in the distribution depends on
openssl 0.9.7, but the python package has no dependency on the
openssl097 package.
Max.
signature.asc
Description: OpenPGP digital signature
Thrall, Bryan wrote:
... And in fact, disabling DEP for setup.exe fixes the problem. So, it
looks like setup.exe is trying to execute some memory that Windows
thinks it shouldn't be (the invalid this pointer, probably, but why then
is it invalid at that point and valid after the segfault?).
Lapo Luchini wrote:
Max Bowsher wrote:
Total guess here, but are you trying to use DESTDIR? PHP is just weird,
and you have to use INSTALL_ROOT instead. In fact, I have vague
recollections of DESTDIR actually doing something else entirely, in PHP.
Mhh, nope.. I'm in fact using your script
Lapo Luchini wrote:
Max Bowsher wrote:
There was one additional fix I had made locally but got around to
updating the tarballs on my server
OK, thanks =)
BTW: have you had this problem? and you solved it how?
% ./php-5.2.0-0.1.sh install strip pkg spkg
Installing PHP SAPI module
Lapo Luchini wrote:
Max Bowsher wrote:
Direct package URLs:
http://jabberwock.vm.bytemark.co.uk/~maxb/cygphp/release/php/php-5.1.4-0.3-src.tar.bz2
Obviously, I'll bump the 0.3 release number up to 1 once GTG is achieved.
Why --without-sqlite? It doesn't work? As an extension, is very
Lapo Luchini wrote:
Max Bowsher wrote:
Why --without-sqlite? It doesn't work? As an extension, is very very
handy IMHO.
I don't remember why, sorry.
Yup, it doesn't work, but I found the issue (previously seen it: in os.h
must REMOVE the cygwin ifdef, so that unix.h is used by default
Reini Urban wrote:
I have /usr/bin/makedb.exe
Is this 'makedb' name in any way official?
Personally, I am opposed to renaming 'remake' to 'makedb' (in both the
executable and package name) as a Cygwin-local change, if that's what it is.
Max.
signature.asc
Description: OpenPGP digital
Corinna Vinschen wrote:
On Aug 12 23:13, Max Bowsher wrote:
The recent thread about remake suggests it would be a good idea to
define some actual official package naming rules: exactly what things
are considered valid for the name, version, and release fields in a package.
I propose
Dave Korn wrote:
On 14 August 2006 09:58, Max Bowsher wrote:
Corinna Vinschen wrote:
On Aug 12 23:13, Max Bowsher wrote:
The recent thread about remake suggests it would be a good idea to
define some actual official package naming rules: exactly what things
are considered valid for the name
The recent thread about remake suggests it would be a good idea to
define some actual official package naming rules: exactly what things
are considered valid for the name, version, and release fields in a package.
I propose:
A package NVR identifier is name-version-release - three fields
Reini Urban wrote:
Max Bowsher schrieb:
To my mind, a DLL is strongly preferable, because all packages using the
library pick up any fixes automatically, instead of requiring a
recompilation themselves.
fcgi does not build out of the box as shared library on any target.
Almost no other
Reini Urban wrote:
Max Bowsher schrieb:
Reini Urban wrote:
I want to contribute and maintain the fastcgi library.
I compiled it just as static library, which is useful for apache2,
lighttpd, ruby, php and clisp. Maybe I might be persuaded to maintain a
dll (libfcgi0) also.
I do not see how
Reini Urban wrote:
I want to contribute and maintain the fastcgi library.
I compiled it just as static library, which is useful for apache2,
lighttpd, ruby, php and clisp. Maybe I might be persuaded to maintain a
dll (libfcgi0) also.
I do not see how it would be useful for apache2.
Why a
Dr. Volker Zell wrote:
cut here
#!/bin/bash
mkdir cadaver
cd cadaver
wget http://de.geocities.com/vzell1/cygwin/setup.hint.zip
mv setup.hint.zip setup.hint
wget
* Max Bowsher?
expat Max Bowsher?
libxml2*Yaakov S?
libxslt Yaakov S?
I'd like to ask Yaakov, Max, Dave and Yitzchak, are you taking over,
or are you still considering to take over? It would be nice to have
that sorted out
Christopher Faylor wrote:
On Sun, Jun 11, 2006 at 03:52:26PM +0100, Max Bowsher wrote:
Three of my library packages are going to be becoming obsolete in the
medium-term future.
libapr0 and libaprutil0 and their development packages apr and apr-util
are already used only by [prev] software
Yaakov S (Cygwin Ports) wrote:
Max Bowsher wrote:
Yaakov suggested changing php-apache2 to apache2-php. I countered that
php-apache2 is consistent with the subversion-apache2 we already have,
and that it more useful to have all the possibilities for using PHP
grouped together, than to have
Three of my library packages are going to be becoming obsolete in the
medium-term future.
libapr0 and libaprutil0 and their development packages apr and apr-util
are already used only by [prev] software.
libneon24 is used solely by [curr] cadaver, and [prev] subversion.
I'm soliciting opinions
cadaver is now the sole package whose [curr] version depends on libneon24.
Please could it be rebuilt against neon 0.25.x, which will entail
bumping the dependency to libneon25. Thanks!
Max.
signature.asc
Description: OpenPGP digital signature
I now have a PHP package which builds in a manner I think is adequate
for release. I still haven't addressed the matter of loadable
extensions, so it is mandatory to install postgresql to install PHP at
all, but given the regular interest in PHP shown on the cygwin ML, I
think people are going to
Yaakov S (Cygwin Ports) wrote:
Max Bowsher wrote:
# php-apache2
category: Web
requires: php apache2
external-source: php
sdesc: PHP: Hypertext Preprocessor (Apache 2 module)
ldesc: PHP is a widely-used general-purpose scripting language that is
especially suited for Web development and can
I'm nearing actually posting PHP packages for review.
One final issue that I've encountered: The default PHP configuration
file path for a from-source build is /usr/lib/php.ini . Which is just
plain weird. I'll make that /etc/php.ini if that suits everyone?
Max.
signature.asc
Description:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrew Schulman wrote:
I'm packaging a new release of lftp. The default config file
(/etc/lftp.conf) is slightly different from the one in the previous release.
This raises a problem: how should I determine whether to replace the old
config
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yaakov S (Cygwin Ports) wrote:
Gerrit P. Haase wrote:
I'll keep maintaining the following if there is no interest:
antiword
db*/libdb*
check
indent
enscript
exif/libexif
expat
freeglut
jasper
libfpx
libmng
libwmf
libxml2
libxslt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reini Urban wrote:
Due to popular request I'll change the postgresql layout from the big
monolithic singular package to a layout as used in debian for 8.1
This will make it easier for the packages xemacs and php at first,
and for users it will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just a quick status update:
I've now successfully hacked the buildsystem to produce the cgi-fcgi
version of the binary a well as the cli version.
I intend to try to tweak the build into producing a core DLL before
posting any prospective packages -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reini Urban wrote:
Well, postgresql is currently one big monolithic package.
To make dependencies easier, I could provide the cygpg.dll client lib
in a seperate libpg8 package, so that you could talk to a remote
postgresql server at least.
ok?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Max Bowsher wrote:
Given the above caveats, do you think I should proceed with the ITP
process, or not?
Lapo Luchini wrote:
I had tought to do this ITP too, but as I'm already enough behind
schedule with existing packages I always delayed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't have much of a liking for PHP myself, but seeing the large
quantity of people who _do_ want it, and being the apache2 maintainer, I
feel like I ought to at least make a bit of an effort to make it available.
So: I have prospective PHP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini wrote:
Category Devel is huge, really huge.
The main reason behind this (from my point of view, of course) is
that it contains both tools (compilers, versioning systems, and so
on) and libraries (the many many many lib*) useful for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Peshansky wrote:
On Thu, 16 Mar 2006, Max Bowsher wrote:
Speaking of in-use DLLs, did you have a chance to look at
http://cygwin.com/ml/cygwin-apps/2006-03/msg00060.html?
OK, I'll have a look.
So, I think we should always rename preremove
Igor Peshansky wrote:
On Tue, 14 Mar 2006, Max Bowsher wrote:
Igor Peshansky wrote:
On Thu, 9 Mar 2006, Dave Korn wrote:
On 09 March 2006 23:14, Max Bowsher wrote:
* script.cc (Script::run): Fix inverted test for abnormal exit.
Do not rename to .done unless completed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Peshansky wrote:
Hi,
The current format for installed.db is (except the first line)
PKG-NAME TARBALL-NAME 0
which setup tries to parse as
package-name filename filesize src-filename srcsize
(with src-filename and srcsize never
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Korn wrote:
On 10 March 2006 17:20, Christopher Faylor wrote:
On Mon, Mar 06, 2006 at 05:00:45AM +0100, Bas van Gompel wrote:
Op Wed, 16 Nov 2005 23:29:50 +0100 (MET) schreef Bas van Gompel
in n2m-g.dlgdit.3vsvtmt.1atbuzzy-box.bavag:
Now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Korn wrote:
Hi all, here's my contribution to the current setup patchfrenzy!
The radiobuttons for Prev, Keep, Curr, Exp at the top of the package chooser
should never have been radiobuttons. They don't select a persistent mode,
they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eugene Kotlyarov wrote:
Hello
tree-plus.bmp and tree-minus.bmp files are missing from
setup-2.523.tar.bz2 snapshot, though they exist in CVS. It gives an
error when building setup.exe.
Thanks for the report.
Fixed.
Max.
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bas van Gompel wrote:
Here this is again, but with the modifications to threebar.cc/res.rc
split off into a separate patch (See
n2m-g.dr1l0a.3vva69r.1atbuzzy-box.bavag).
ChangeLog-entry: (Please fix the at.)
2006-01-23 Bas van Gompel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bas van Gompel wrote:
In order to be able to see the names of the ini-file being parsed, and
the location being dowloaded from (if/when that patch
([EMAIL PROTECTED]) gets applied), I
suggest making better use of the available window-width.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Peshansky wrote:
2006-01-23 Igor Peshansky [EMAIL PROTECTED]
* script.cc (Script::run): Fix inverted test for abnormal exit.
Ping (attached as setup-script-exit-code-fix.patch-1).
Clearly correct, please commit.
2006-01-31 Igor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a test release of Apache 2.2 ready to upload.
Am I correct in thinking I'm supposed to send [test] announcements to
[EMAIL PROTECTED] not to [EMAIL PROTECTED] ?
Thanks,
Max.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have test Apache 2.2 packages happily serving on my machine right now.
There are a few issues regarding the transition which I want to air
ahead of time for possible comments:
1. Configuration file compatibility
Apache 2.0 configuration files
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bas van Gompel wrote:
Op Thu, 01 Dec 2005 15:28:49 + schreef Max Bowsher
in 438F16B1.5000805atukf.net:
:
: Buzz wrote:
: Hallo setup-maintainer,
:
: Op Tue, 8 Nov 2005 22:50:55 +0100 (MET) schreef Bas van Gompel
: in [EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Buzz wrote:
Hallo setup-maintainer,
Op Tue, 8 Nov 2005 22:50:55 +0100 (MET) schreef Bas van Gompel
in [EMAIL PROTECTED]:
: Hi,
:
: Here is a patch to make setup tell where files are actually being
: downloaded from.
:
:
:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bas van Gompel wrote:
Op Wed, 30 Nov 2005 22:18:54 + schreef Max Bowsher
in 438E254E.5070101atukf.net:
: Bas van Gompel wrote:
[patch]
: The terrifying irony here, is that after all this icky pointer
: manipulation, the calculated value
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bas van Gompel wrote:
Op Thu, 01 Dec 2005 16:45:31 + schreef Max Bowsher
in 438F28AB.80109atukf.net:
: Bas van Gompel wrote:
: Op Wed, 30 Nov 2005 22:18:54 + schreef Max Bowsher
: in 438E254E.5070101atukf.net:
[patch for site.cc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Current libxslt chokes on some contructs in the DocBook FO stylesheet.
The bug is fixed in libxslt CVS.
Please consider applying the patch, and releasing 1.1.15-2.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Pechtchanski wrote:
Brian, can we please get a 2.521 setup snapshot out? Thanks,
Igor
Done.
http://cygwin.com/setup/
Max.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Pechtchanski wrote:
On Wed, 30 Nov 2005, Max Bowsher wrote:
Igor Pechtchanski wrote:
Brian, can we please get a 2.521 setup snapshot out? Thanks,
Igor
Done.
http://cygwin.com/setup/
Perfect, thanks.
Igor
P.S. Should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bas van Gompel wrote:
Hi,
While looking at site.cc I noticed a check where dot[3] might
point past the end of the allocated string. this may cause false
matches or even a segfault. I suggest following:
2005-10-24 Bas van Gompel [EMAIL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Carl Karsten wrote:
When I run setup-2.521.exe (I think older version too), the step that
asks for Local Package Directory has a text box that could be bigger,
which would be good considering that a default value of
C:\Documents and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi - a note to the Berkeley DB package maintainers:
* A new patch release for the 4.3.x series is available: 4.3.29.
* A new minor release series is available: 4.4.16.
Max.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Cygwin)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Pechtchanski wrote:
On Thu, 24 Nov 2005, Max Bowsher wrote:
I'm preparing a new Apache 2 release, and want to include a conf.d
arrangement to allow additional module packagess to install
configuration fragments in a useful way.
So far, my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Morrison wrote:
On Fri, November 25, 2005 6:08 am, Igor Pechtchanski wrote:
On Thu, 24 Nov 2005, Max Bowsher wrote:
I'm preparing a new Apache 2 release, and want to include a conf.d
arrangement to allow additional module packagess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm preparing a new Apache 2 release, and want to include a conf.d
arrangement to allow additional module packagess to install
configuration fragments in a useful way.
So far, my tentative proposal is:
Include /etc/apache2/conf.d/*.conf in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Igor Pechtchanski wrote:
On Sat, 19 Nov 2005, Max Bowsher wrote:
Summary: The addition of the 'logging' g-b-s feature introduced a bug:
Errors during phases of package building do not halt the build, so that
an error during 'make' or 'make install
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. Volker Zell wrote:
Max Bowsher writes:
Dr. Volker Zell wrote:
Max, would it be possible to recompile neon so that it picks up the
new
openssl package ?
Refreshing neon is of course, not a problem.
Thanks
the 'pkg'
operation running, and producing flawed package files.
If no one has time to fix the logging feature properly right now, could
we just revert the logging feature from g-b-s CVS HEAD until someone does?
Thanks,
Max.
=== Full text of earlier part of thread follows: ===
Max Bowsher wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Franke wrote:
What would you think about an autoconf-like approach generating a
package-VER.sh script from some package.sh.in (yes, no version).
Then fixes and new features will be added to only one generation tool
(autogbs ?-)) which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim O'Callaghan wrote:
Hi,
Sorry about the delay with getting back to this stuff.
I'd like to ask a few quick questions before i send my formal ITP's
1) should i send a separate ITP email for each one or one for all of them?
Choose based on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim O'Callaghan wrote:
On Fri, Nov 18, 2005 at 05:57:14AM -0700, Eric Blake wrote:
3) If a package needs a specific tool to build it, such as asciidoc being
needed for
git documentation, does it also need to be supported or not? if so does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. Volker Zell wrote:
I would like to contribute and maintain the cadaver package:
* http://www.webdav.org/cadaver/ (Homepage)
Max, would it be possible to recompile neon so that it picks up the new
openssl package ?
Refreshing neon is of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Franke wrote:
Corinna Vinschen wrote:
[...]
Looks pretty much ok, except
- I don't like the versioning scheme. You should keep the normal Cygwin
subversion intact (counting from 1) and put the `pre2005...' string
into the main
Igor Pechtchanski wrote:
On Sat, 29 Oct 2005, Max Bowsher wrote:
Please forgive me if this has already been discussed - I've been
time-limited to scanning subject lines only recently.
Bourne shells consider only the exit status of the last command in a
pipeline when determining
Please forgive me if this has already been discussed - I've been
time-limited to scanning subject lines only recently.
Bourne shells consider only the exit status of the last command in a
pipeline when determining $? - this means that the addition of lots of |
tee somefile will cause errors
The (adhoc?) standard for package file names, which for the most part is
followed, is:
NAME-VERSION-RELEASE.tar.bz2 -- for binary packages
NAME-VERSION-RELEASE-src.tar.bz2-- for source packages
VERSION and RELEASE should not contain '-' characters.
NAME is allowed to contain '-'
Christopher Faylor wrote:
On Mon, Sep 26, 2005 at 01:06:58PM +0200, Corinna Vinschen wrote:
clear
This comes from ncurses doesn't it? Is it being purposely dropped from
the
ncurses distribution? Chuck?
The clear program that ships with ncurses is packaged as clearn.exe, to
avoid
Corinna Vinschen wrote:
LIST 3: PACKAGES WITHOUT REPLY FROM MAINTAINER SO FAR
=
...
x11
There is no package named 'x11'.
There is a directory called 'X11' into which all X-related packages are
grouped, which is probably how this entry
Hack Kampbjorn wrote:
Corinna Vinschen wrote:
On Sep 21 20:23, Hack Kampbjorn wrote:
Hack Kampbjorn:
keychain
ncftp
wget
But my last windows computer at home is being hit by a deathstar battle
station. And I will don't read cygwin mail at work even that I do have a
windows desktop there
Robert Richter wrote:
I didn't really intend to package PHP, but having got this far, I sort of
feel I ought to.
Which brings me to two major issues concerning any potential Cygwin PHP
package:
1) Two apache versions.
I've no interest in Apache 1.3.x. Can I just package PHP for 2.x, and
worry
Corinna Vinschen wrote:
Below are the results as of today 2005-09-19. It would be helpful if all
maintainers could scan this lists again,
LIST 2: PACKAGES WITHOUT REPLY FROM MAINTAINER SO FAR
=
par
typespeed
ucl
upx
A transcription
I personally have no need for PHP, but I know it's a very widely used piece
of software.
After John Morrison's recent mention of PHP in passing, I decided to do a
quick estimate of how difficult getting PHP working on Cygwin would be. To
cut a long story short, I got a bit carried away, and
John Morrison replied to me privately (accidentally, I presume).
I'm forwarding the message to cygwin-apps@ to maintain threading:
Original Message below:
---
Hi Max,
On Fri, September 16, 2005 11:27 pm, Max Bowsher wrote:
The current /etc/profile does not permit the use
John Morrison wrote:
Hi Max,
On Fri, September 16, 2005 11:27 pm, Max Bowsher wrote:
The current /etc/profile does not permit the use of symlinks in
/etc/profile.d/ - it ignores them.
Sorry, didn't realise. If I change the line
/bin/find /etc/profile.d -type f -iname '*.sh' -or -iname
Eric Blake wrote:
Sorry, didn't realise. If I change the line
/bin/find /etc/profile.d -type f -iname '*.sh' -or -iname '*.zsh'
to be
/bin/find -L /etc/profile.d -type f -iname '*.sh' -or -iname '*.zsh'
would that fix things? (The -L tells find to follow the link and make
decisions based
The current /etc/profile does not permit the use of symlinks in
/etc/profile.d/ - it ignores them.
Unfortunately, even if this was fixed in the package, existing installs
wouldn't get fixed, because /etc/profile is handled via /etc/defaults :-(
/me gives up on finding a way for
Corinna Vinschen wrote:
So, ALL maintainers of Cygwin packages,
please reply to this mail within the next six weeks,
including a list of ALL packages you maintain.
apache2
apache2-devel
apache2-manual
apr
libapr0
apr-util
libaprutil0
doxygen
neon (soon to be renamed to neon24)
Christopher Faylor wrote:
I'm thinking about adding a maintainer field to setup.hint which would
have meaning only in setup.hint but would allow us to more easily track
who maintains what. It would look like this:
Maintainer: Chris Faylor
Perhaps keep maintainer all lower-case, for
Taking a look at my main Subversion binary package, I've noticed that the
gettext message catalogs account for almost half the size of the tarball -
and over half of the unpacked size.
Approx sizes (.mo files/other files)
Compressed 458kB / 467kB
Unpacked 2.0MB / 1.5MB
I'm wondering whether
Christopher Faylor wrote:
On Tue, Sep 13, 2005 at 11:30:04PM +0100, Max Bowsher wrote:
Taking a look at my main Subversion binary package, I've noticed that the
gettext message catalogs account for almost half the size of the
tarball -
and over half of the unpacked size.
Approx sizes (.mo
Eric Blake wrote:
According to Igor Pechtchanski on 9/8/2005 8:50 AM:
Ugh. Couldn't this be installed into /usr/share/neon-*/man, and handled
by judicious manipulation of the MANPATH?
This sounds good to me - judicious use of the alternatives system to
select which script in /etc/profile.d/
Neon is a library that is still in development, with an API which is still
evolving. Thus, it is necessary to package multiple versions to support
programs which will not always build against the latest API.
For the most part this is not a problem. The current libpng packages use the
Why does the 'bugfix' 2.510.2.2 release have no code changes in the CVS
repository at all, versus the 2.510.2.1 release?
What's going on? Does 2.510.2.2 contain uncommitted changes? If so, please
commit them!
Max,
Brian Dessent wrote:
However, I think the larger question is do we *really* need a release
branch? I only did it this time because it seems to be established
procedure, but I see no real reason to continue it. I guess it made
sense in prior times when there were destabilising changes being
Christopher Faylor wrote:
On Thu, Sep 08, 2005 at 06:23:16PM +0100, Max Bowsher wrote:
Brian Dessent wrote:
However, I think the larger question is do we *really* need a release
branch? I only did it this time because it seems to be established
procedure, but I see no real reason to continue
Max Bowsher wrote:
Why does the 'bugfix' 2.510.2.2 release have no code changes in the CVS
repository at all, versus the 2.510.2.1 release?
What's going on? Does 2.510.2.2 contain uncommitted changes? If so, please
commit them!
... and later I come to an email explaining. Oops. Should have
Igor Pechtchanski wrote:
Well, destabilizing changes *are* made to HEAD occasionally, but testing
is the way to deal with those... I'd suggest tagging each release, but
only converting the tag to a branch for back-ported fixes from the trunk.
That way, regular releases will have the trunk
1 - 100 of 891 matches
Mail list logo
