Op Fri, 18 Nov 2005 23:20:25 -0500 schreef Charles Wilson
in 437EA809.30204atcwilson.fastmail.fm:
: Igor Pechtchanski wrote:
[new gbs features]
: Well, the problem is, logging is a decorator: it decorates the existing
: functions. Unless you want a whole new build-with-logging() function
:
Igor Pechtchanski wrote:
[...]
P.S. It'd be a different story if we were using an 'engine' with
external overrides, like mingwports or cgf's netrel(?) -- then mods to
the engine to provide new features would be distinct from the
package-specific overrides. But gbs ain't like that.
-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
Charles Wilson wrote:
I'd like to make a request: gbs is getting out of control with this
feature and that feature added. Some of these tasks are NEVER going to
be performed by anyone other than the primary maintainer: has anyone
actually used 'foo.sh list' or 'foo.sh depends'?
I use these
[Resummited to cygwin-apps on request of Igor]
Hi,
the build-script of the smartmontools package creates the
Cygwin/package-*.README file from
srcdir/CYGWIN-PATCHES/package.README.in by replacing VER/REL with the
current version/release numbers.
This might be useful for other packages to
Christian Franke wrote:
the build-script of the smartmontools package creates the
Cygwin/package-*.README file from
srcdir/CYGWIN-PATCHES/package.README.in by replacing VER/REL with the
current version/release numbers.
This might be useful for other packages to avoid extra editing of README
On Fri, 18 Nov 2005, Charles Wilson wrote:
Christian Franke wrote:
the build-script of the smartmontools package creates the
Cygwin/package-*.README file from
srcdir/CYGWIN-PATCHES/package.README.in by replacing VER/REL with the
current version/release numbers.
This might be useful
