public inbox for gentoo-perl@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vadim Konovalov <vadim@vkonovalov.ru>
To: gentoo-perl@lists.gentoo.org
Cc: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] Perl ebuilds needing updates (95)
Date: Fri, 30 Dec 2005 00:32:57 +0300	[thread overview]
Message-ID: <1135891977.5827.11.camel@localhost> (raw)
In-Reply-To: <1135855400.13022.20.camel@sys947.dtic.mil>

> > Re: [gentoo-perl] Perl ebuilds needing updates (95)
> > 
> ...
> > > Total packages suspected as outdated: 95
> > So what ?
> 
> *ouch*
> 
> Well, 2 things really. First - this list is for discussing perl and
> related issues in gentoo. Second, our most frequent bug report is
> "module Foo is out of date, please bump, kthnxbye."

Could you please advice, what should I do to convince to add Tcl and
Tcl::Tk CPAN modules to the list of supported modules?

In the very brief:

 - I maintain those on CPAN; I can try creating ebuilds myself and then
support (if needed)
 - those two are interconnection modules between Perl and Tcl/Tk
 - similar to "tclperl" Tcl extension, but other way round (make full
Tcl/Tk available to Perl)
 - provide same GUI capabilities as perl/Tk do, but with much more
flexibility

I would be grateful for help on this.

Best regards,
Vadim.


-- 
gentoo-perl@gentoo.org mailing list



WARNING: multiple messages have this Message-ID (diff)
From: Vadim Konovalov <vadim@vkonovalov.ru>
To: gentoo-perl@gentoo.org
Cc: gentoo-perl@lists.gentoo.org
Subject: Re: [gentoo-perl] Perl ebuilds needing updates (95)
Date: Fri, 30 Dec 2005 00:32:57 +0300	[thread overview]
Message-ID: <1135891977.5827.11.camel@localhost> (raw)
Message-ID: <20051229213257.uY5QAXXHo6y9j2AoAc1SJA0pWSzZNCxc0jAS9JPQJRg@z> (raw)
In-Reply-To: <1135855400.13022.20.camel@sys947.dtic.mil>

> > Re: [gentoo-perl] Perl ebuilds needing updates (95)
> > 
> ...
> > > Total packages suspected as outdated: 95
> > So what ?
> 
> *ouch*
> 
> Well, 2 things really. First - this list is for discussing perl and
> related issues in gentoo. Second, our most frequent bug report is
> "module Foo is out of date, please bump, kthnxbye."

Could you please advice, what should I do to convince to add Tcl and
Tcl::Tk CPAN modules to the list of supported modules?

In the very brief:

 - I maintain those on CPAN; I can try creating ebuilds myself and then
support (if needed)
 - those two are interconnection modules between Perl and Tcl/Tk
 - similar to "tclperl" Tcl extension, but other way round (make full
Tcl/Tk available to Perl)
 - provide same GUI capabilities as perl/Tk do, but with much more
flexibility

I would be grateful for help on this.

Best regards,
Vadim.


-- 
gentoo-perl@gentoo.org mailing list



  parent reply	other threads:[~2005-12-29 21:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26  7:32 [gentoo-perl] Perl ebuilds needing updates (95) Michael Cummings
2005-12-26 18:33 ` J.A.
2005-12-29 11:23   ` Michael Cummings
2005-12-29 12:13     ` Antoine Raillon
2005-12-29 12:21       ` Michael Cummings
2005-12-29 12:35         ` Antoine Raillon
2005-12-29 12:54           ` Michael Cummings
2005-12-29 13:03             ` Antoine Raillon
2005-12-29 21:32     ` Vadim Konovalov [this message]
2005-12-29 21:32       ` Vadim Konovalov

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=1135891977.5827.11.camel@localhost \
    --to=vadim@vkonovalov.ru \
    --cc=gentoo-perl@gentoo.org \
    --cc=gentoo-perl@lists.gentoo.org \
    /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