Group :: Desenvolvimento/Perl
RPM: perl-UNIVERSAL-moniker
Main Changelog Spec Patches Sources Download Gear Bugs e FR Repocop
%define dist UNIVERSAL-moniker
Name: perl-%dist
Version: 0.08
Release: alt1
Summary: UNIVERSAL::moniker
License: GPL or Artistic
Group: Development/Perl
URL: %CPAN %dist
Source: %dist-%version.tar.gz
BuildArch: noarch
# Added by buildreq2 on Thu Jul 14 2005
BuildRequires: perl-Lingua-EN-Inflect perl-devel
%description
Class names in Perl often don't sound great when spoken, or look good when
written in prose. For this reason, we tend to say things like "customer" or
"basket" when we are referring to C<My::Site::User::Customer> or
C<My::Site::Shop::Basket>. We thought it would be nice if our classes knew what
we would prefer to call them.
%prep
%setup -q -n %dist-%version
%build
%perl_vendor_build
%install
%perl_vendor_install
%files
%doc README Changes
%perl_vendor_privlib/UNIVERSAL*
%changelog
…
Todas as alterações você pod ver aqui
Name: perl-%dist
Version: 0.08
Release: alt1
Summary: UNIVERSAL::moniker
License: GPL or Artistic
Group: Development/Perl
URL: %CPAN %dist
Source: %dist-%version.tar.gz
BuildArch: noarch
# Added by buildreq2 on Thu Jul 14 2005
BuildRequires: perl-Lingua-EN-Inflect perl-devel
%description
Class names in Perl often don't sound great when spoken, or look good when
written in prose. For this reason, we tend to say things like "customer" or
"basket" when we are referring to C<My::Site::User::Customer> or
C<My::Site::Shop::Basket>. We thought it would be nice if our classes knew what
we would prefer to call them.
%prep
%setup -q -n %dist-%version
%build
%perl_vendor_build
%install
%perl_vendor_install
%files
%doc README Changes
%perl_vendor_privlib/UNIVERSAL*
%changelog
…
Todas as alterações você pod ver aqui