Re: CPAN - resolving ownership of Set-Object distribution

[Sam Vilain]

Yes, please do. I do everything I used to do in Perl using python or go
these days.

Thanks and regards,
Sam

On Thu, Sep 10, 2020 at 7:11 AM Neil Bowers  wrote:

>
>
>
>
>
>
>
>
>
>
>
>
> Hi Sam,
>
>
>
>
>
> I’m one of the PAUSE admins. I’m working on resolving all the cases where
> a distribution has the first-come permissions shared between multiple
> people. PAUSE tries to make sure this doesn’t happen now, but in the past
> it was easy for it to happen, when someone with co-maint adds a new module
> to a distribution.
>
>
>
>
>
> For the Set-Object distribution, you have first-come on the lead module,
> but Reini (RURBAN, copied on this email) has first-come on the reat. He has
> also done all releases since 2013, so I wonder if it makes sense to give
> him co-maint on all modules?
>
>
>
>
>
> If you’re happy with this, I can do it on your behalf. You’ll retain
> co-maint. Is that ok?
>
>
>
>
>
> Cheers,
>
>
> Neil
>
>
>
>
>
>
>
>
>

Re: Primary maintainer for XML::Assert

[Sam Vilain]

As the original author, I approve of this idea!

Cheers,
Sam

On Jun 27, 2017 1:43 AM, "Simon Green"  wrote:

Hello,

It appears[1] that the XML::Assert module has no owner. Can the PAUSE
user 'NZRS'[2] please be made the primary maintainer? If this is not
possible, can you make 'SAMV' the primary maintainer, and I'll talk to
him about taking it over.

Thanks.

--
Simon

[1] https://metacpan.org/permission/module/XML::Assert
[2] As you can see in the POD for the module, NZRS have copyright on the
module.

Re: Primary maintainer for XML::SRS and XML::EPP

[Sam Vilain]

I also approve of this ownership. NZRS sponsored the development of these
modules and is the natural custodian of this Perl DNS Registry code.

Sam

On Jun 27, 2017 1:55 AM, "Simon Green"  wrote:

> Hello,
>
> It appears[1][2] that the XML::SRS and XML::EPP modules have no owner.
> Can the PAUSE user 'NZRS'[3] please be made the primary maintainer? If
> this is not possible, can you make 'SAMV' the primary maintainer, and
> I'll talk to him about taking it over.
>
> Thanks.
>
> --
> Simon
>
> [1] https://metacpan.org/permission/module/XML::SRS
> [2] https://metacpan.org/permission/module/XML::EPP
> [3] As you can see in the POD for the modules, NZRS have copyright on
> the module.
>
>
>

Re: PAUSE indexer report SAMV/Set-Object-1.03.tar.gz

[Sam Vilain]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, can someone push this through please?  I have permissions now, but
I can't re-upload the same file twice.

Cheers,
Sam.

On Fri, 23 May 2003 01:13, you wrote:
 The following report has been written by the PAUSE namespace indexer.
 Please contact [EMAIL PROTECTED] if there are any open questions.
   Id: mldistwatch 342 2003-04-03 09:55:14Z k

User: SAMV (Sam Vilain)
   Distribution file: Set-Object-1.03.tar.gz
 Number of files: 26
  *.pm files: 3
  README: Set-Object-1.03/README
   Timestamp of file: Thu May 22 12:49:31 2003 UTC
Time of this run: Thu May 22 13:13:23 2003 UTC

 The following packages have been found in the distro:

 Set::Object
 version: 1.03
 in file: Set-Object-1.03/Object.pm
  status: Not indexed because permissions missing. Visit PAUSE and
  click View Permissions to find the legitimate
  maintainer(s).

 __END__

- -- 
Sam Vilain, [EMAIL PROTECTED]

The outward freedom that we shall attain will only be in exact
proportion to the inward freedom to which we may have grown at a given
moment. And if this is a correct view of freedom, our chief energy
must be concentrated on achieving reform from within.
 -- Mahatma Gandhi

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj7d9BIACgkQpCUwqQW1LxM/CwCglVtffW9wcOdgdU5sV+ZqrFar
iMQAoPbMMRrriBM3kkksE+nhmRrPgqSM
=UjD3
-END PGP SIGNATURE-

modules/00modlist.long.html

[Sam Vilain]

Is there a reason this file hasn't been updated in 10 months?
--
   Sam Vilain, [EMAIL PROTECTED] WWW: http://sam.vilain.net/
7D74 2A09 B2D3 C30F F78E  GPG: http://sam.vilain.net/sam.asc
278A A425 30A9 05B5 2F13

Hi, I'm a .signature virus!  Copy me into your ~/.signature, please!

[ANNOUNCE] Lingua::Translate version 0.01

[Sam Vilain]

Hi all,

I have just PAUSE'd Lingua::Translate 0.01.  This module provides a
framework for natural language translation software.

Currently, there is one back-end using Babelfish, and very soon I hope to
add SysTran enterprise (ie, the back-end software that Babelfish uses) to
the list.

It's as simple as:

  use Lingua::Translate;

  my $xl8r = Lingua::Translate-new(src = en, dest = de);

  print $xl8r-translate(I do so like green eggs and ham, thank you, 
 .thank you, Sam I am!), \n;
  # prints Ich also wie grüne Eier und Schinken, Ihnen zu danken, danken
  # Ihnen, SAM, die ich bin!

I would appreciate any feedback, particularly on the interface.

Cheers,
Sam.

Pod::Constants modules list entry

[Sam Vilain]

Hi there,

Pod::Constants is now getting fairly well developed, and I'd like a
modules list entry for it.  It's description is:

::Constants adpfp Simpler extraction of constants from Pod

It probably wants to be in section 2 of the modules list under
Documentation Tools.

I have a little written up on it, and the man page in HTML at my web
site at http://sam.vilain.net/pm/

Cheers,
Sam.

Re: Pod::Constants

[Sam Vilain]

On Wed, 31 Oct 2001 19:07:48 -0500
Kirrily Robert [EMAIL PROTECTED] wrote:

 Has this already been done?
Pod::Constants - Include constants from POD
 I don't know, but will it solve the eternal $VERSION problem?

Sure, but you have to work around MakeMaker:

=head2 MODULE RELEASE

$VERSION = 1.05

=cut

use vars qw($VERSION);
use Pod::Constants -trim = 1, 'MODULE RELEASE' = \$VERSION;
BEGIN { $VERSION =~ s/^\$VERSION\s*=\s*// };

Sam

Pod::Constants 0.01

[Sam Vilain]

Hi there,

I've just uploaded Pod::Constants.  It lets you write:

use Pod::Constants 'my section' = \$my_ref;

=head1 my section

This data will go into $my_ref

=cut

It is based on Pod::Parser.  If this is accepted into the Perl 5 modules
list, please make the entry read as follows:

::Constantsadpfp Quickly set a constant from a POD sectionSAMV

Cheers,
--
   Sam Vilain, [EMAIL PROTECTED] WWW: http://sam.vilain.net/
7D74 2A09 B2D3 C30F F78E  GPG: http://sam.vilain.net/sam.asc
278A A425 30A9 05B5 2F13

Hi, I'm a .signature virus!  Copy me into your ~/.signature, please!

 PGP signature

Pod::Constants

[Sam Vilain]

Has this already been done?

NAME
   Pod::Constants - Include constants from POD

SYNOPSIS
use vars qw($myvar);
use Pod::Constants -trim = 1,
'Pod Section Name' = \$myvar;

=head2 Pod Section Name

This string will be loaded into $myvar

=cut

DESCRIPTION
   This module is for when you have constants in your code,
   but you want to keep them in the documentation so that
   when they change you only have to update them in one
   place.

   Pod::Constants uses Pod::Parser to do the parsing of the
   source file.  It has to open the source file it is called
   from, and does so directly either by lookup in %INC or
   from $0 if the caller is main.

   I have made this code only allow the Pod Section Name to
   match `head1', `head2' and `item' POD sections.  If you
   have a good reason why you think it should match other POD
   sections, drop me a line and if I'm convinced I'll put it
   in the standard version.

AUTHOR
   Sam Vilain, [EMAIL PROTECTED]

BUGS/TODO
   Is there any value in being able to import structured data
   from POD sections, perhaps?  Maybe extracting tabular
   information into arrays or hashes?

   What about doing nasty things to the caller's symbol
   table, so they don't need to use vars?


 Constants.pm

PAUSE access request

[Sam Vilain]

Hi there.

My name is Sam Vilain, I've been programming Perl for about 3 years and
now it's time for me to start putting things back.  

The first module I'm going to contribute is called Class::Tangram, which
acts as a base class for Tangram persistent objects.  You place the
section of the Tangram schema particular to each object within the package
scope as $Object::schema, run Class::Tangram::import_schema(Object), and
then you get:

   - Object-new(field = value) style constructor
   - $o-set_field(value) field updating methods (implemented via
 AUTOLOAD)
   - $o-get_field() accessors (also aliased as $o-field())
   - $o-clear_refs, which explicitly breaks any references in attributes,
 empties Set::Object containers, etc.

The set_field method performs simple type checking, so eg you can't set an
int to a string, or a ref to a non-blessed object.

It also extends the tangram schema specification by allowing you to
specify, for each attribute, a check_func (a CODE ref that is called
with the argument as first parameter and dies if there is a problem)
and an init_default (either a basic data type that is used as a default
or a code ref returing the default).

In this respect, it is somewhat similar to Class::Contract, but you get
the ability to store the objects in an RDBMS via Tangram instantly.  In
fact, I will eventually try to roll support for this into Class::Contract.

I would like to use the PAUSE id of SAMV.

Cheers,
--
   Sam Vilain, [EMAIL PROTECTED] WWW: http://sam.vilain.net/
7D74 2A09 B2D3 C30F F78E  GPG: http://sam.vilain.net/sam.asc
278A A425 30A9 05B5 2F13

Hi, I'm a .signature virus!  Copy me into your ~/.signature, please!

 PGP signature