submission of GnuPG::Interface
This is the second sending of this message; I have not gotten response back from the first. I've recently created the first release of GnuPG::Interface, the successor to my PGP::GPG::MessageProcessor, and am looking for approval. I already have an account on CPAN (FTOBIN). Desired contribution: GnuPG::Interface Description: GnuPG::Interface is a heavily object-oriented interface to interacting with the GNU Privacy Guard. It also consists of a rich object-oriented GnuPG key structure. DLSI: bdpO 44-char description:OO interface to GNU Privacy Guard I have discussed this module a little on the [EMAIL PROTECTED] mailing list, but have mainly received input based on its predecessor, PGP::GPG::MessageProcessor. GnuPG::Interface is also a central module for another program of mine, pgpenvelope. Thank you for your time in advance. -- Frank Tobin http://www.uiuc.edu/~ftobin/ "To learn what is good and what is to be valued, those truths which cannot be shaken or changed." Myst: The Book of Atrus
User update for JONG
(This Mail was generated by the server https://pause.kbx.de/pause/authenquery;ACTION=edit_cred automatically) Record update in the PAUSE users database: userid: [JONG] fullname: [Jong Park] email: [[EMAIL PROTECTED]] was [[EMAIL PROTECTED]] homepage: [http://biosophy.org/] was [] cpan_mail_alias: [publ] Data were entered by JONG (Jong Park). Please check if they are correct. Thanks, The Pause
User update for FDESAR
(This Mail was generated by the server https://pause.kbx.de/pause/authenquery;ACTION=edit_cred automatically) Record update in the PAUSE users database: userid: [FDESAR] fullname: [Francois Desarmenien] email: [[EMAIL PROTECTED]] was [[EMAIL PROTECTED]] homepage: [] cpan_mail_alias: [publ] Data were entered by FDESAR (Francois Desarmenien). Please check if they are correct. Thanks, The Pause
Mail::Audit
I've been using this for six months or so now. It's cool. Mail::AuditRdpO Toolkit for constructing mail filtersSIMON -- `And when you've been *plonk*ed by Simon C., you've been *plonked* by someone who knows when, and why, and how.' - Mike Andrews, asr
Re: [OFF TOPIC] Anyone at modules@perl.org ?
On 26 Apr 2000, (Andreas J. Koenig) wrote: > What about adding this paragraph to 04pause.html: > > Please consult these archive before you post a module proposal. The > fulltext search capabilities of the archive should help you to find > similar suggestions and contact addresses. [EMAIL PROTECTED] is low > volume, so your search in the archive is quite targetted. The module > list maintainers themselves are mostly lurkers. You need not wait > for a response. Generally a lack of response can be taken as > acceptance of the module name being proposed. Andreas, A few weeks ago I wrote asking for my module list to be updated. Any idea what's happened to that? My current list is: CGI::XMLForm Win32::ASP It needs to add: Apache::MimeXML DBIx::AnyDBD Time::Object Win32::ADO XML::PYX XML::XPath XML::miniXQL Let me know if you need any descriptions. -- Fastnet Software Ltd. High Performance Web Specialists Providing mod_perl, XML, Sybase and Oracle solutions Email for training and consultancy availability. http://sergeant.org http://xml.sergeant.org
Re: submission of GnuPG::Interface
On Wed, Apr 26, 2000 at 02:25:04AM -0500, Frank Tobin wrote: > This is the second sending of this message; I have not gotten response > back from the first. > > I've recently created the first release of GnuPG::Interface, the successor > to my PGP::GPG::MessageProcessor, and am looking for approval. I already > have an account on CPAN (FTOBIN). > > Desired contribution: GnuPG::Interface > > Description: > > GnuPG::Interface is a heavily object-oriented interface to interacting > with the GNU Privacy Guard. It also consists of a rich object-oriented > GnuPG key structure. The `Interface' part seems redundant to me. What else would a GnuPG module be? Peace, * Kurt Starsinic ([EMAIL PROTECTED]) -- Senior Network Engineer * | `People keep pretending they can make things deeply | |hierarchical, categorizable and sequential when they can't.| |Everything is deeply intertwingled.' -- Ted Nelson |
Re: [OFF TOPIC] Anyone at modules@perl.org ?
On Wed, Apr 26, 2000 at 10:50:50AM -0400, [EMAIL PROTECTED] wrote: > On Wed, Apr 26, 2000 at 02:20:04PM +0200, Andreas Koenig wrote: > > Please consult these archive before you post a module proposal. The > > fulltext search capabilities of the archive should help you to find > > similar suggestions and contact addresses. [EMAIL PROTECTED] is low > > volume, so your search in the archive is quite targetted. The module > > list maintainers themselves are mostly lurkers. You need not wait > > for a response. Generally a lack of response can be taken as > > acceptance of the module name being proposed. > > I suggest one additional line: > > If you want a quick response, be sure to ask if anybody actually > reads the list. This is guaranteed to produce at least ten > responses in rapid suggestion (none of which will respond to your > proposal). Does this actually work? LOL :-) -- "May the best description of competition prevail." via, but not speaking for Deutsche Bank
Please add WWW::BBSWatch to modules list
I have uploaded a module to PAUSE at https://pause.kbx.de/pub/PAUSE/authors/id/T/TA/TAYERS/WWW-BBSWatch-0.02.tar.gz Can it be added to the modules list? It belongs in section 15) World Wide Web, HTML, HTTP, CGI, MIME etc, in the WWW:: subsection The entry is Name DSLI Description Info - - ::BBSWatch adpO email WWW bulletin board postingsTAYERS Thanks very much and Hope you have a very nice day, :-) Tim Ayers ([EMAIL PROTECTED]) PAUSE ID = TAYERS
IPC::BashEm???
A while ago on p5p there was some discussion of writing a 'shellpipe'
routine that would allow you to do subprocess management using
a sh-like interface.
Below is a start at it I'm tentatively calling IPC::BashEm. Suggestions
for better names appreciated.
- Barrie
package IPC::BashEm ;
#
# Copyright (c) 1999 by Barrie Slaymaker, [EMAIL PROTECTED]
#
# You may distribute under the terms of either the GNU General Public
# License or the Artistic License, as specified in the README file.
#
=head1 NAME
IPC::BashEm - bash (bourne again shell) command line emulation
=head1 SYNOPSIS
use IPC::BashEm ;
## Read from / write to scalars
bashem( 'cat', '<', \$stdin, '>', \$stdout, '2>', \$stderr ) ;
## Read from / write using subroutine handlers
bashem(
'cat',
'<', \&get_some_in,
'>', \&catch_some_out,
'2>', \&catch_some_err
) ;
=head1 DESCRIPTION
Provides limited support for bash shell command line redirection constructs.
=head2 Supported constructs
=over
=item ARG, N>ARG
Redirects any output the child emits via file descriptor N
to a scalar variable, subroutine, file handle, or file name.
N may be 1 (stdout), or 2 (stderr). If not provided, N defaults to 1.
ARG may be a reference to a scalar or a subroutine. For instance:
bashem( 'ls', '2>', sub { $err_out .= $_[0] } ) ;
does the same basic thing as:
bashem( 'ls', '2>', \$err_out ) ;
Redirecting output to a file is not yet implemented.
The subroutine will be called each time some data is read from the child.
=back
=head1 RETURN VALUE
Returns the result of the last command in chain, as returned by waitpid().
This will not be true when a non-blocking option is added and used.
=head1 LIMITATIONS
Very incomplete, still growing.
No support for ';', '&', '|', '{ ... }', etc: only one subprocess is
supported yet.
No non-blocking mode.
=cut
use strict ;
use Exporter ;
use vars qw( $VERSION @ISA @EXPORT $debug ) ;
$VERSION = '0.001' ;
@ISA = qw( Exporter ) ;
## We use @EXPORT for the end user's convenience: there's only one function
## exported, it's homonymous with the module, it's an unusual name, and
## it can be suppressed by "use IPC::BashEm () ;".
@EXPORT = qw( bashem ) ;
use Carp ;
use Errno qw( EAGAIN ) ;
use File::Spec ;
use FileHandle ;
use IPC::Open3 ;
use UNIVERSAL qw( isa ) ;
###
my %cmd_cache ;
sub debug {
return unless $debug ;
print STDERR 'bashem: ', @_, "\n" ;
}
sub _search_path($) {
my ( $cmd_name ) = @_ ;
return $cmd_name if File::Spec->file_name_is_absolute( $cmd_name ) ;
return $cmd_cache{$cmd_name} if exists $cmd_cache{$cmd_name} ;
my @searched_in ;
unless ( exists $cmd_cache{$cmd_name} ) {
## This next bit is Unix specific, unfortunately.
## There's been some conversation about extending File::Spec to provide
## a universal interface to PATH, but I haven't seen it yet.
for ( split( /:/, $ENV{PATH}, -1 ) ) {
$_ = "." unless length $_ ;
push @searched_in, $_ ;
my $prospect = File::Spec->catfile( $_, $cmd_name ) ;
if ( -x $prospect ) {
$cmd_cache{$cmd_name} = $prospect ;
debug( 'found ', $prospect ) ;
last ;
}
}
}
return $cmd_cache{$cmd_name} if exists $cmd_cache{$cmd_name} ;
croak "Command '$cmd_name' not found in " . join( ", ", @searched_in ) ;
}
sub empty($) { ! defined $_[0] && length $_[0] }
sub _parse {
my @errs ;
my @out ;
## The UNSUPPORTED => 1 ops are not fatal, since we want to test the
## grammar. _setup catches them and turns them fatal.
while ( @_ ) { for ( shift ) {
eval {
## Do >&, <& first so that
if ( /^(\d+)>&(\d+)$/ ) {
push @out, {
UNSUPPORTED => 1,
TYPE=> '>&',
KFD1=> $1,
KFD2=> $2,
} ;
}
elsif ( /^(\d+)<&(\d+)$/ ) {
push @out, {
UNSUPPORTED => 1,
TYPE=> '<&',
KFD1=> $1,
KFD2=> $2,
} ;
}
elsif ( /^(?:>&|&>)(.*)$/ ) {
my $dest = length $1 ? $1 : shift ;
die "'$_' missing a destination\n" if empty $dest ;
push @out, {
UNSUPPORTED => 1,
TYPE=> '>2>&1',
DEST=> $dest,
MODE=> 'trunc',
} ;
}
elsif ( /^(\d*)<(.*)$/ ) {
my $source = length $2 ? $2 : shift ;
die "'$_' missing a source\n" if empty $source;
push @out, {
TYPE => '<',
KFD=> length $1 ? $1 : 0,
SOURCE => $source,
} ;
}
elsif ( /^(\d*)>(>?)(.*)$/ ) {
my $dest = length $3 ? $3 : shift ;
die "'$_'
User update for MUNSINGER
(This Mail was generated by the server https://pause.kbx.de/pause/authenquery;ACTION=edit_cred automatically) Record update in the PAUSE users database: userid: [MUNSINGER] fullname: [Doug Munsinger] email: [[EMAIL PROTECTED]] was [[EMAIL PROTECTED]] homepage: [] cpan_mail_alias: [publ] Data were entered by MUNSINGER (Doug Munsinger). Please check if they are correct. Thanks, The Pause
tar file organization
I've just registered and received the password. I have finished my modules, and I want to submit it to PAUSE, but I have one problem... I don't know how to organize my tar file. Where do I put the modules, the README, and so on???... Can anybody help me? daniel ruoso
Re: tar file organization
On Wed, Apr 26, 2000 at 04:35:24PM +, Daniel Ruoso wrote: > I've just registered and received the password. > I have finished my modules, and I want to submit it to PAUSE, but I have one >problem... > > I don't know how to organize my tar file. Where do I put the modules, the README, >and so on???... > > Can anybody help me? If you've created a Makefile.PL, and you've set $VERSION appropriately, then you do something like this: perl Makefile.PL make dist Then you'll have a tarball suitable for uploading. Peace, * Kurt Starsinic ([EMAIL PROTECTED]) -- Senior Network Engineer * | `It is always possible to aglutenate multiple separate problems | | into a single complex interdependent solution. In most cases | | this is a bad idea.' - Ross Callon |
Re: submission of GnuPG::Interface
Kurt D. Starsinic, at 10:53 -0400 on Wed, 26 Apr 2000, wrote: > > GnuPG::Interface is a heavily object-oriented interface to interacting > > with the GNU Privacy Guard. It also consists of a rich object-oriented > > GnuPG key structure. > > The `Interface' part seems redundant to me. What else would a GnuPG > module be? I have to admit I haven't been able to come up with another name to succintly describe the module. The unadorned name "GnuPG" is already taken by another module (as described in my message); I simply attached "::Interface" so that mine could be distinct, even though redundant. Coming up with 'fun', 'unixy', or even 'original-yet-nondescriptive' names doesn't seem to be a tradition on CPAN. All modules seen to directly describe their functionality. This another reason I created the bland and redundant name "GnuPG::Interface". Referring to history, I haven't seen other situation on CPAN where two modules, relying on another program, attempt to perform the same function. There is some committal to the name GnuPG::Interface already, such as project on SourceForge.net having been established, with an undetermined number of people people already using the module, so renaming it is not a matter I wish to be taken lightly. I think that although the name is redundant, it both describes the functionality and is unique. -- Frank Tobin http://www.uiuc.edu/~ftobin/ "To learn what is good and what is to be valued, those truths which cannot be shaken or changed." Myst: The Book of Atrus
Re: [OFF TOPIC] Anyone at modules@perl.org ?
On Wed, Apr 26, 2000 at 11:04:55AM -0400, Joshua N Pritikin wrote: > On Wed, Apr 26, 2000 at 10:50:50AM -0400, [EMAIL PROTECTED] wrote: > > On Wed, Apr 26, 2000 at 02:20:04PM +0200, Andreas Koenig wrote: > > > Please consult these archive before you post a module proposal. The > > > fulltext search capabilities of the archive should help you to find > > > similar suggestions and contact addresses. [EMAIL PROTECTED] is low > > > volume, so your search in the archive is quite targetted. The module > > > list maintainers themselves are mostly lurkers. You need not wait > > > for a response. Generally a lack of response can be taken as > > > acceptance of the module name being proposed. > > > > I suggest one additional line: > > > > If you want a quick response, be sure to ask if anybody actually > > reads the list. This is guaranteed to produce at least ten > > responses in rapid suggestion (none of which will respond to your > > proposal). > > Does this actually work? Sometimes. > LOL :-) I'm not sure who's currently on the modules list, but if you guys aren't, perhaps you'd like to join... part of the problem is that there are few experienced people on the list and those that are have zero free time. Tim.
Registration request
Hello,
This is a registration request to CPAN according to the guidelines written in
http://www.cpan.org/modules/04pause.html
Name: Coalescent Technologies Inc.
Email: [EMAIL PROTECTED]
Preferred user-ID: CTI
Description:
Coalescent Technologies Inc. would like to contribute a template parser
toolkit,
Name DSLI DescriptionInfo
Text::TPL bdph parse templates; supports loops; supports SSI CTI
(This information is according to guidelines written in
http://www.cpan.org/modules/00modlist.long.html#1)ModuleListing)
This module has only been used internally, therefore it has not been
publicly discussed. It was initiated in year 1998 and was
continuously enhanced since.
Please reply to [EMAIL PROTECTED]
Sincerely yours,
Boris Krivulin,
Coalescent Technologies Inc.
