You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucy.apache.org by "Marvin Humphrey (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/07 21:00:57 UTC

[lucy-issues] [jira] [Resolved] (LUCY-213) Explicit version number for each Perl module

     [ https://issues.apache.org/jira/browse/LUCY-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marvin Humphrey resolved LUCY-213.
----------------------------------

    Resolution: Fixed
    
> Explicit version number for each Perl module
> --------------------------------------------
>
>                 Key: LUCY-213
>                 URL: https://issues.apache.org/jira/browse/LUCY-213
>             Project: Lucy
>          Issue Type: Bug
>          Components: Perl bindings
>    Affects Versions: 0.3.0 (incubating)
>            Reporter: Marvin Humphrey
>            Assignee: David E. Wheeler
>            Priority: Minor
>             Fix For: 0.3.1 (incubating), 0.4.0
>
>
> The Perl/CPAN dependency system is organized around versions for each Perl
> module/package, rather than versions for each distribution.  Up until now, we
> have only maintained a version in Lucy.pm; in order to accommodate Perl/CPAN,
> we must make a version available for every public Perl module.
> The solution is to add an explicit version number to each Perl package which
> is visible to CPAN.  To reduce errors, version numbers will be modified using
> the devel/bin/update_version script, and the Perl build system will validate
> versions for all published modules when building the CPAN tarball.
> Additionally, we will require a more recent version of Module::Build when
> building the CPAN tarball.  (The fact that the CPAN release of Lucy 0.3.0 was
> built with an earlier version of M::B than 0.2.2 caused problems related to
> this version numbering issue.)
> Dev list discussion: http://s.apache.org/1ZJ http://s.apache.org/MCn

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira