Corinna schrieb:
Gerrit,
On Jun 14 15:58, Gerrit P. Haase wrote:
For a start, we (cgf and I, that is) grant Gerrit the right, to add new
package to the Cygwin net distro without review and by just getting one
vote, if nobody else vetos the package within a week.
Wow, thanks!
Btw.,
Hi Voker,
PS: By the way I vote for the /opt/gnome2 hirarchy for this package.
please start a separate thread to discuss this issue.
Gerrit
--
=^..^=
Yaakov schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. Volker Zell wrote:
| Hi Gerrit, during the build stage I get the following error:
|
| make[3]: Leaving directory `/usr/src/glib-2.4.2/.build/gobject'
| echo #ifndef __G_MARSHAL_H__ xgen-gmh \
| echo #define
Frédéric schrieb:
On Tue, 15 Jun 2004, Yaakov Selkowitz wrote:
Dr. Volker Zell wrote:
| PS: By the way I vote for the /opt/gnome2 hirarchy for this package.
As I've stated already, this is also my opinion.
To make this easier for Gerrit to decide, I've written the attached
scripts which
Hi Yaakov,
The build script needs a couple of changes; the patch is attached. The
Applied, though , if you don't have gtk-doc installed won't this be
automatically disabled? Anyway, I'll try to provide gtk-doc as a
package.
rest of us don't have a working gtk-doc installation, so
-
On Jun 16 10:35, Gerrit P. Haase wrote:
Corinna schrieb:
Btw., you still need to send a mail that a package should get uploaded.
Don't wait for people seeing that automatically, please ;-)
I have an account and may upload myself;)
Oh, I didn't know that. That makes it much easier.
Hi Yaakov,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerrit P. Haase wrote:
| Renamed repackaged tarballs:
| http://anfaenger.de/cygwin/gtk+/glib/glib2-2.4.2-1.tar.bz2
| http://anfaenger.de/cygwin/gtk+/glib/setup.hint
|
|
Volker,
[...]
Here a windows popup box appears with glib-genmarshal.exe - Unable To
Locate DLL
The dynamic link library cygglib-2.0-0.dll could not be found in the
specified path.
Forget the patch with the static library. Though it works for
glib-genmarshal it will fail later with
Gerrit P Haase writes:
Forget the patch with the static library. Though it works for
glib-genmarshal it will fail later with gobject-scan which is more
problematic. Unless someone figures out how to build gobject-scan
statically I need to find another solution.
Too late, I
On Wed, 16 Jun 2004, Gerrit P. Haase wrote:
Igor schrieb:
On Mon, 14 Jun 2004, Gerrit P. Haase wrote:
Hello,
I want to contribute/maintain ATK.
Canonical website: http://www.gtk.org/
Runtime package setup.hint:
===
category: Libs Devel
requires: cygwin libiconv2 libintl2
Hi all,
In libwmf's sdesc and ldesc should Windows and Microsoft
have a stroke through the o? (sorry to whoever's language
uses this character, I really should know what it's called!)
Just wondering,
J.
Igor Pechtchanski wrote:
P.S. FWIW, another idea I had, akin to Max's python approach, was to
actually append a (wrapped) GBS patch to the GBS instead of changing the
script directly, and have the GBS detect that fact and apply the patch to
itself, then running the resulting script (piping it to
Gerrit P. Haase wrote:
No and yes, and IIRC, the script doesn't work because the libtool-devel
creates a dummy executable, so if there are glib-genmarshal and
glib-genmarshal.exe in the same directory, glib-genmarshal.exe will be
executed at first and since it is a dummy it fails.
Actually,
Gerrit P. Haase wrote:
It's such things that makes some people think GLib is a GNOME
or graphical library and should be avoided at all.
I agree. There are some overlappings though. But since there are
already some of the core libraries of the GNOME desktop in /usr we
should just stay with it.
I
Gerrit P. Haase wrote:
Forget the patch with the static library. Though it works for
glib-genmarshal it will fail later with gobject-scan which is more
problematic. Unless someone figures out how to build gobject-scan
statically I need to find another solution.
The simple solution would be to
Well, yes, I agree that if you really anticipate having to maintain
multiple packages from the outset, and want to keep more or less the same
build procedure for each of them (helps if they are related), you should
probably start already with something more sophisticated than the gbs.
I don't
So, to answer that question, why not something like this:
# --- BEGIN_DEFS ---
if [ -f ${FULLPKG}.defs ]; then
. ${FULLPKG}.defs
fi
# --- END_DEFS ---
So, if my source package name is foo.tar.Z, then I can put the
[snip]
following in my defs file:
# Maintainer defs
17 matches
Mail list logo
