You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Everett Toews (JIRA)" <ji...@apache.org> on 2012/07/04 22:04:35 UTC
[jira] [Created] (VCL-602) RPM spec file for VCL
Everett Toews created VCL-602:
---------------------------------
Summary: RPM spec file for VCL
Key: VCL-602
URL: https://issues.apache.org/jira/browse/VCL-602
Project: VCL
Issue Type: Improvement
Components: database, vcld (backend), web gui (frontend)
Affects Versions: 2.3
Environment: CentOS 6.2
Reporter: Everett Toews
Priority: Minor
All the dependencies, CPAN modules included, can be obtained from the EPEL and RPMForge repositories. If the project is going to support RHEL and CentOS only then providing a RPM could allow you to remove the requirement to run (and maintain) the perl libs install script.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (VCL-602) RPM spec file for VCL
Posted by "Curtis C. (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/VCL-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Curtis C. updated VCL-602:
--------------------------
Attachment: vcl.spec
This is an intial spec file for VCL 2.2.1 on CentOS 6. All dependencies can be satisfied by a combination of the base, rpmforge, and epel repositories.
It breaks the vcl tar file into 3 rpms...docs (essentially the sql files), the web frontend, and the management node so they can be split up across servers if desired.
> RPM spec file for VCL
> ---------------------
>
> Key: VCL-602
> URL: https://issues.apache.org/jira/browse/VCL-602
> Project: VCL
> Issue Type: Improvement
> Components: database, vcld (backend), web gui (frontend)
> Affects Versions: 2.3
> Environment: CentOS 6.2
> Reporter: Everett Toews
> Priority: Minor
> Labels: install, rpm
> Attachments: vcl.spec
>
>
> All the dependencies, CPAN modules included, can be obtained from the EPEL and RPMForge repositories. If the project is going to support RHEL and CentOS only then providing a RPM could allow you to remove the requirement to run (and maintain) the perl libs install script.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira