From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] Perl distributions (in preparation of Perl 5.22)
Date: Mon, 22 Jun 2015 16:59:00 -0000 [thread overview]
Message-ID: <87mvzrfzlp.fsf@Rainer.invalid> (raw)
In-Reply-To: <87a8wt3rg0.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 25 May 2015 12:02:55 +0200")
Achim Gratz writes:
> That leaves the following Perl distributions in the hands of Yaakov,
> mainly because they are related to library or tool packages he owns.
>
> perl-Authen-SASL
> perl-Cairo
> perl-Cairo-GObject
> perl-Glib
> perl-Glib-Object-Introspection
> perl-Gnome2
> perl-Gnome2-Canvas
> perl-Gnome2-GConf
> perl-Gnome2-Rsvg
> perl-Gnome2-VFS
> perl-Gnome2-Vte
> perl-Gnome2-Wnck
> perl-GStreamer
> perl-GStreamer-Interfaces
> perl-Gtk2
> perl-Gtk2-GladeXML
> perl-Gtk2-Notify
> perl-Gtk2-SourceView2
> perl-Gtk2-Spell
> perl-Gtk2-Unique
> perl-Gtk2-WebKit
> perl-Gtk3
> perl-MailTools
> perl-Net-SMTP-SSL
> perl-Pango
> perl-PAR-Packer
> perl-SGMLSpm
> perl-Tk
> perl-Tk-Canvas-GradientColor
> perl-Tk-ColoredButton
> perl-Tk-EntryCheck
> perl-Tk-Getopt
> perl-Tk-Pod
>
> There are a few Perl distribution packages that are captive in another
> source package. The hopefully complete list of such packages:
>
> perl-Graphics-Magick
> perl-gv
> perl-Image-Magick
> perl-ming
> perl-Net-Libproxy
> perl-Xfce4-Xfconf
> perl-zinnia
>
> This means that again Yaakov as well as Marco and Volker need to
> re-release those.
I would appreciate if you could indicate whether the builds are
finished. In particular I didn't hear anything from Volker yet.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
next prev parent reply other threads:[~2015-06-22 16:59 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 10:03 Achim Gratz
2015-05-25 15:24 ` Achim Gratz
2015-05-29 19:26 ` Achim Gratz
2015-05-29 19:44 ` Yaakov Selkowitz
2015-05-29 19:46 ` Yaakov Selkowitz
2015-05-29 19:57 ` Achim Gratz
2015-05-29 20:43 ` Yaakov Selkowitz
2015-05-29 20:55 ` Achim Gratz
2015-05-29 19:50 ` Achim Gratz
2015-05-31 16:00 ` Marco Atzeri
2015-05-31 18:59 ` Achim Gratz
2015-06-22 16:59 ` Achim Gratz [this message]
2015-06-22 21:46 ` Marco Atzeri
2015-06-23 5:38 ` Achim Gratz
2015-07-02 21:13 ` Marco Atzeri
2015-07-03 5:36 ` Achim Gratz
2015-06-26 23:09 ` Yaakov Selkowitz
2015-06-30 3:05 ` Yaakov Selkowitz
2015-06-30 5:04 ` Achim Gratz
2015-07-04 10:46 ` Achim Gratz
2015-07-04 12:31 ` Marco Atzeri
2015-07-04 19:34 ` David Rothenberger
2015-07-05 6:02 ` Achim Gratz
2015-07-05 13:26 ` Ken Brown
2015-07-05 18:32 ` Yaakov Selkowitz
2015-07-05 19:44 ` Achim Gratz
2015-07-05 20:01 ` Ken Brown
2015-07-27 22:43 ` Uploading packages built against Perl 5.2.2 [Was: [ITA] Perl distributions (in preparation of Perl 5.22)] Adam Dinwoodie
2015-07-28 5:43 ` Uploading packages built against Perl 5.2.2 [ Achim Gratz
2015-07-28 6:40 ` Marco Atzeri
2015-07-28 11:18 ` Corinna Vinschen
2015-07-28 16:18 ` Achim Gratz
2015-07-28 16:36 ` Corinna Vinschen
2015-07-28 17:06 ` David Rothenberger
2015-07-28 17:20 ` Achim Gratz
2015-07-28 16:23 ` Eric Blake
2015-07-28 16:36 ` Ken Brown
2015-07-28 16:40 ` Corinna Vinschen
2015-07-28 17:31 ` Ken Brown
2015-07-28 16:37 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvzrfzlp.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).