[Bug 250804] Review Request: perl-Encode-Detect - Detects the encoding of data
bugzilla at redhat.com
bugzilla at redhat.com
Fri Aug 24 15:44:40 UTC 2007
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: perl-Encode-Detect - Detects the encoding of data
Alias: perl-Encode-Detect
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=250804
cweyl at alumni.drew.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cweyl at alumni.drew.edu
Alias| |perl-Encode-Detect
------- Additional Comments From cweyl at alumni.drew.edu 2007-08-24 11:44 EST -------
(In reply to comment #2)
> Yeah, the Fedora Packaging Guidelines don't speak that much on building perl
> modules. What I used, I originally copied from a RHEL package. (I have
> multiple other perl packages I want to contribute, which is why I'm waiting for
> this one to be reviewed before I proceed.)
There is a collection of perl packaging "best practices" under
https://fedoraproject.org/wiki/PackagingDrafts/Perl . Note that these aren't
official guidelines, but are generally what perl reviewers will use when looking
at a package.
> The reason why I don't use %{module} et. al. macros in Source0: is because I
> always download the source by copying-and-pasting it into a wget command. I
> actually like having the additional edit; it forces me to Do The Right Thing
> whenever I grab a new version of the package.
An interesting approach :) I find "spectool -g foo.spec" helps to download new
versions of sources with slightly fewer mouse/key strokes than wget.
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the Fedora-package-review
mailing list