New bugmail proposal...
by Warren Togami
http://news.gmane.org/gmane.mail.spam.spamassassin.devel
On second thought, I am thinking it may not be too bad to auto-CC this
mailing list on all perl* FC bugs. It works fairly well for
spamassassin's development list. The perl* bug load is fairly small
compared to spamassassin, and immediate notification to the group of all
activity would help to keep everyone better informed.
I am thinking to exclude a few types of bug mail like "I'm adding myself
CC but not making a comment". There are many categories that can be
disabled in the account bugmail preferences that I can experiment with.
The security embargo thing isn't too much of a problem. We can just ask
bressers not to clone the FC security bug until embargo is lifted, or
maybe dkl can devise some way of excluding the list until embargo lifts
automatically.
Any objections to this?
Warren Togami
wtogami(a)redhat.com
18 years, 11 months
ANNOUNCE: Bug Mail
by Warren Togami
You are advised to edit your mail filters to filter
fedora-perl-devel-list mail into a folder before you filter Bugzilla
mail, if you want to avoid a bunch of duplicate mail in your bug folder.
Warren Togami
wtogami(a)redhat.com
18 years, 11 months
Overriding core Perl modules
by Kenneth Porter
This has already been touched on in a couple of other threads, more as a
matter of figuring out which modules should be removed from core and made
separate packages. A different approach is to use the site mechanism and
library path or some extension of it to allow replacement modules to
coexist with those in core.
Using cpanflute2 one can use "--installdirs=site" to create a package that
installs to the site directories instead of the vendor directories. This is
almost sufficient to do the job, but there's no "site" directory for man
pages, so one will get install-time conflicts for those.
<https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=142837>
My own involvement is in installing MIMEDefang (http://mimedefang.org/),
which requires a raft of Perl modules, some of which are updates to those
in core. Most were easy enough to repackage with cpanflute2, but a couple
required a bit of intervention to deal with unusual tarball names and
conflicts with Perl core packaging.
18 years, 11 months