Build environment
by Doran L. Barton
My experimentation with software collections has transformed into a big
project where we will probably be building Perl (5.16, most likely) packages
for RHEL 5 and 6 for deployment across dozens, perhaps hundreds, of servers.
Up until now, I've been building these packages by hand in a CentOS 6 VM on my
laptop, but I realize to do it "right," I really need to set up a dedicated
build environment, possibly using something like Koji.
Additionally, what do you think about making perl514 or perl516 packages
available via EPEL? Once we have a build system in place, could we contribute
our packages to EPEL or should we just set up our own public repository?
Your thoughts would be appreciated.
--
Doran L. Barton <doran(a)bluehost.com> - Senior Developer, Bluehost, RHCE
"Please take yourself to anything you like."
-- Seen at restaurant entrance in Japan
11 years, 9 months
perl.spec problems - fixed
by Doran L. Barton
I discovered /usr/lib/rpm/perl.prov.stack and /usr/lib/rpm/perl.req.stack were
installed with rwx------ (700) permissions as part of the perl514-build
package. After I changed the permissions on those two scripts, packages could
be built (as a non-priviledged user) with the proper dependency resolution.
--
Doran L. Barton <doran(a)bluehost.com> - Senior Developer, Bluehost
"Not to be used as protection from a tornado."
-- A label seen on a blanket
11 years, 9 months
perl.spec for perl514
by Doran L. Barton
One thing I've noticed that would help is if the individual CPAN modules that
are included as sub-packages in the perl.spec each had a Provides: line like
this:
Provides: %{?scl_prefix}perl(Compress::Raw::Bzip2) = %{version}
I don't know why 'cpanspec' doesn't add this line normally. It seems valuable.
--
Doran L. Barton <doran(a)bluehost.com> - Senior Developer, Bluehost
"Bank Drive-in Window Blocked by Board"
-- Headline seen in a newspaper
11 years, 9 months
