m (→Requirements) |
|||
| Line 19: | Line 19: | ||
|- | |- | ||
|''<code>use base</code> constructs correctly evaluated''||<pre>use base 'XXX';</pre>||<pre>perl(base)</pre>||<pre>perl(base) | |''<code>use base</code> constructs correctly evaluated''||<pre>use base 'XXX';</pre>||<pre>perl(base)</pre>||<pre>perl(base) | ||
perl(XXX)</pre>|| | perl(XXX)</pre>|| | ||
|- | |- | ||
|''No duplicate provides''|| || || || | |''No duplicate provides''|| || || || | ||
|- | |- | ||
|''Mo*se subclassing''||<pre>extends 'Some::Class';</pre>||None.||<pre>perl(Some::Class)</pre>|| | |''Mo*se subclassing''||<pre>extends 'Some::Class';</pre>||None.||<pre>perl(Some::Class)</pre>|| | ||
| Line 40: | Line 40: | ||
|- | |- | ||
|''Catalyst and other plugin syntax''||<pre>use Catalyst qw/ | |''Catalyst and other plugin syntax''||<pre>use Catalyst qw/ | ||
-Debug | -Debug | ||
ConfigLoader | ConfigLoader | ||
Static::Simple/;</pre>||<pre>perl(Catalyst)</pre>||<pre> | Static::Simple/;</pre>||<pre>perl(Catalyst)</pre>||<pre>perl(Catalyst) | ||
perl(Catalyst) | |||
perl(Catalyst::Plugin::ConfigLoader) | perl(Catalyst::Plugin::ConfigLoader) | ||
perl(Catalyst::Plugin::Static::Simple) | perl(Catalyst::Plugin::Static::Simple)</pre>|| | ||
</pre>|| | |||
|- | |- | ||
|''Ability to include/exclude''|| || || || | |''Ability to include/exclude''|| || || || | ||
Revision as of 01:44, 20 February 2009
Brain dump. Comments welcome and appreciated, on the talk page.
Current Status
rpmbuild has been able to automatically generate Perl requires and provides for some time now. In most cases, it works just fine, but in many cases it fails us, and we end up having to filter them. There have also been significant advances in Perl since the autoprov/req scripts were written, resulting in language constructs that are simply not recognized. (Moose and other metaclass-oriented frameworks are a great example of this). This has resulted in a disproportionately large percentage of Perl packages in Fedora having some sort of wrapper around the autoprov/req scripts.
It's time for new autoprov/req scripts.
Questions
- Should we try to normalize the versions?
Requirements
Apologies to those of us without widescreen monitors :)
| Requirement | Example | Current Auto-Reqs | Target Auto-Reqs | Compat? |
use base constructs correctly evaluated |
use base 'XXX'; |
perl(base) |
perl(base) perl(XXX) |
|
| No duplicate provides | ||||
| Mo*se subclassing | extends 'Some::Class'; |
None. | perl(Some::Class) |
|
| Mo*se roles | with 'Some::Class'; # multiple roles at once with 'Role::A', 'Role::B'; |
None. | perl(Some::Class) perl(Role::A) perl(Role::B) |
|
| Mo*se traits | ...in an attribute specification:... traits => [ 'X', 'Y' ] |
None. | perl(Moose::Meta::Custom::Trait::X) perl(Moose::Meta::Custom::Trait::Y) |
|
| Mo*se metaclasses | ||||
| Catalyst and other plugin syntax | use Catalyst qw/ -Debug ConfigLoader Static::Simple/; |
perl(Catalyst) |
perl(Catalyst) perl(Catalyst::Plugin::ConfigLoader) perl(Catalyst::Plugin::Static::Simple) |
|
| Ability to include/exclude |
No duplicate requires
We often see duplicate requires. These are harmless, except in the case where one requires is versioned and another unversioned.
This might need to be addressed at a higher level than perl.prov... Maybe some sort of RPM-level Lua script? (see, e.g. RPM_scripting_with_Lua)
use base syntax
Both use base and use parent style constructs need to be recognized and handled. (They're basically the same thing, anyways.)
| Example | Current | Target | Compat? | Comment |
Mo*se syntax
Both Moose and Mouse have similar subclassing and roles syntax; only Moose has metaclasses and traits (metaclass roles).
extends
- Multiple classes can be specified
- not possible to specify version with this syntax
with
- Multiple classes can be specified
- not possible to specify version with this syntax
metaclasses
Class, attribute, methods.
| Example | Current | Target | Compat? | Comment |
traits
Class, attribute, methods.
| Example | Current | Target | Compat? | Comment |
Catalyst and other plugin syntax
Note that it is quite common for a Catalyst app to have a multi-line "use Catalyst" statement; we need to be able to deal with multi-line use statements.
| Example | Current | Target | Compat? | Comment |
use Catalyst qw/ -Debug ConfigLoader Static::Simple/; |
perl(Catalyst) |
perl(Catalyst) perl(Catalyst::Plugin::ConfigLoader) perl(Catalyst::Plugin::Static::Simple) |