headers
Alberto Simões | 2 Mar 2010 22:55
Picon
Favicon
Gravatar

Politics and Method to include modules under inc/

Hello

Some users of my Text::BibTeX module requested me to include some
modules that are only required for the build process into the inc/
directory.

As I am not experienced on that, some questions arose:

- what are the politics? can I include any module?
- what structure I should use? substitute the lib/Module by inc/Module ?
- how to make MB aware of these modules?
- how to make them not to be indexed by cpan?

Thank you
ambs

--

-- 
Alberto Simões
Permalink | Reply | 1 comment |
headers
Eric Wilhelm | 2 Mar 2010 23:26
Picon

Re: Politics and Method to include modules under inc/

Hi Alberto,

# from Alberto Simões
# on Tuesday 02 March 2010 13:55:

>Some users of my Text::BibTeX module requested me to include some
>modules that are only required for the build process into the inc/
>directory.

Why?  Are they having trouble satisfying configure_requires or 
build_requires?  If you bundle things, you have to rebundle them.

>As I am not experienced on that, some questions arose:
>
>- what are the politics? can I include any module?
>- what structure I should use? substitute the lib/Module by inc/Module
> ? - how to make MB aware of these modules?

You might want to try inc::latest, which allows you to fall back onto 
the bundled copy only if a newer one isn't already on the machine.

If you want to do something more manual, any "use lib '...'" in the 
Build.PL should appear wherever you need it to throughout the build 
process.

Make sure the modules don't show up in 'provides' in your META.yml.

--Eric
--

-- 
software:  a hypothetical exercise which happens to compile.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Johan Vromans | 13 Mar 2010 13:26
Picon
Favicon
Gravatar

Releasing a candidate

Working late to get a release candidate ready for upload.
Change the version number to "2.00.RC1". Yes, with quotes.

    $ perl Build.PL
    ...
    Creating new 'Build' script ... version '2.00.'

Version '2.00.' ?

Did I miss something in the docs about not being able to manifacture
your own version number?

-- Johan
Permalink | Reply | 2 comments |
headers
John Peacock | 14 Mar 2010 03:24

Re: Releasing a candidate

On 03/13/2010 07:26 AM, Johan Vromans wrote:
> Working late to get a release candidate ready for upload.
> Change the version number to "2.00.RC1". Yes, with quotes.

Where?  Did you change that in Build.PL or in the $VERSION assignment in 
the main .pm file?

> Version '2.00.' ?
>
> Did I miss something in the docs about not being able to manifacture
> your own version number?
            ^^^^^^^^^^^^^^

Version number is the applicable phrase there.  Perl doesn't understand 
anything except numbers (and PAUSE/CPAN too as far as I know).  You 
/could/ use version::AlphaBeta (but I wouldn't recommend it).  This 
doesn't really have anything to do with version.pm, per se, but that 
won't help matters (since the parser will explicitly stop at the first 
non-numeric).  Try running `perl -w Build.PL` and see what that tells you.

You cannot just dump random text into $VERSION and expect it to work. 
Among other things, how do you expect tools to sort this release with 
all of the other releases you are making?

John
Permalink | Reply | 1 comment |
headers
Johan Vromans | 14 Mar 2010 14:21
Picon
Favicon
Gravatar

Re: Releasing a candidate

[Quoting John Peacock, on March 13 2010, 21:24, in "Re: Releasing a cand"]
> Where?  Did you change that in Build.PL or in the $VERSION assignment in 
> the main .pm file?

In the main .pm file.
I did work around the problem by adding an explicit dist_version to
Build.PL. 

> You cannot just dump random text into $VERSION and expect it to work. 
> Among other things, how do you expect tools to sort this release with 
> all of the other releases you are making?

print "yes" if "2.00 RC1"  lt "2.00.00";
print "yes" if "2.00(RC1)" lt "2.00.00";

What would your suggestion be to distinctively denote a release
candidate? 

-- Johan
Permalink | Reply | 0 comments |
headers
Gabor Szabo | 27 Mar 2010 12:25
Picon
Gravatar

Adding both mozilla1.0 and mozilla1.1 to the list of licenses

Hi,

http://search.cpan.org/dist/Module-Build/lib/Module/Build/API.pod
lists 'mozilla' as mozilla 1.0 or mozilla1.1

I am now trying to get Bugzilla packaged to CPAN and it is explicitely licensed
under mozilla1.1

Would it be possible to add those two keys to the valid list of values
of the license field?
Software::License http://search.cpan.org/dist/Software-License/
already has them separated.

regards
    Gabor
Permalink | Reply | 5 comments |
headers
David Golden | 27 Mar 2010 12:40
Picon
Gravatar

Re: Adding both mozilla1.0 and mozilla1.1 to the list of licenses

On Sat, Mar 27, 2010 at 7:25 AM, Gabor Szabo <szabgab <at> gmail.com> wrote:
> I am now trying to get Bugzilla packaged to CPAN and it is explicitely licensed
> under mozilla1.1
>
> Would it be possible to add those two keys to the valid list of values
> of the license field?
> Software::License http://search.cpan.org/dist/Software-License/
> already has them separated.

Hi, Gabor.  Just list it as "mozilla" or "open_source" for now.  The
way licenses get handled will be revised when we release the CPAN Meta
2.0 spec later this year.  (And both Mozilla licenses are already
included separately in the valid list in the draft 2.0 spec).

-- David
Permalink | Reply | 4 comments |
headers
Gabor Szabo | 27 Mar 2010 12:45
Picon
Gravatar

Re: Adding both mozilla1.0 and mozilla1.1 to the list of licenses

On Sat, Mar 27, 2010 at 2:40 PM, David Golden <xdaveg <at> gmail.com> wrote:
> On Sat, Mar 27, 2010 at 7:25 AM, Gabor Szabo <szabgab <at> gmail.com> wrote:
>> I am now trying to get Bugzilla packaged to CPAN and it is explicitely licensed
>> under mozilla1.1
>>
>> Would it be possible to add those two keys to the valid list of values
>> of the license field?
>> Software::License http://search.cpan.org/dist/Software-License/
>> already has them separated.
>
> Hi, Gabor.  Just list it as "mozilla" or "open_source" for now.  The
> way licenses get handled will be revised when we release the CPAN Meta
> 2.0 spec later this year.  (And both Mozilla licenses are already
> included separately in the valid list in the draft 2.0 spec).

That's what I did but I expect some arguments from the core Bugzilla developers
and their lawyers. I'll use your point if needed.  Thanks

Gabor
Permalink | Reply | 1 comment |
headers
David Golden | 27 Mar 2010 12:54
Picon
Gravatar

Re: Adding both mozilla1.0 and mozilla1.1 to the list of licenses

On Sat, Mar 27, 2010 at 7:45 AM, Gabor Szabo <szabgab <at> gmail.com> wrote:
> That's what I did but I expect some arguments from the core Bugzilla developers
> and their lawyers. I'll use your point if needed.  Thanks

The license field in Module::Build just sets the same field in
META.yml.  If they don't like 'mozilla' (generic) set it to
'open_source', which is the option for "META.yml spec doesn't support
what I really want to put here".  You still must document the actual
license terms in the code you release.

-- David
Permalink | Reply | 0 comments |
headers
Salve J Nilsen | 27 Mar 2010 16:35
Favicon
Gravatar

Re: Adding both mozilla1.0 and mozilla1.1 to the list of licenses

David Golden said:
> On Sat, Mar 27, 2010 at 7:25 AM, Gabor Szabo <szabgab <at> gmail.com> wrote:
>>
>> I am now trying to get Bugzilla packaged to CPAN and it is 
>> explicitely licensed under mozilla1.1
>>
>> Would it be possible to add those two keys to the valid list of values
>> of the license field?
>> Software::License http://search.cpan.org/dist/Software-License/
>> already has them separated.
>
> Hi, Gabor.  Just list it as "mozilla" or "open_source" for now. 
> The way licenses get handled will be revised when we release the 
> CPAN Meta 2.0 spec later this year.  (And both Mozilla licenses are 
> already included separately in the valid list in the draft 2.0 
> spec).

Nice. How about AGPL_v3?

Is the draft spec available for review somewhere? :)

- Salve, who would like to see a few more licenses added to M:B anyway

--

-- 
#!/usr/bin/perl
sub AUTOLOAD{$AUTOLOAD=~/.*::(\d+)/;seek(DATA,$1,0);print#  Salve Joshua Nilsen
getc DATA}$"="'};&{'"; <at> _=unpack("C*",unpack("u*",':4 <at> ,$'.#     <sjn <at> foo.no>
'2!--"5-(50P%$PL,!0X354UC-PP%/0\`'."\n"));eval "&{' <at> _'}";   __END__ is near! :)
(Continue reading)

Permalink | Reply | 1 comment |

Gmane