[
https://issues.apache.org/jira/browse/CHUKWA-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Yang updated CHUKWA-211:
-----------------------------
Attachment: CHUKWA-211.patch
Ant task to generate rpm has a couple limitations. Ideally, we want to prevent
the use of Makefile in our RPM build to prevent unnecessary nested build
procedures. However, this means we can't create symlink in %install for RPM
build. In addition, Chukwa RPM is design to install in user defined directory.
If version 1 of the RPM build is installed in /usr/local/chukwa-1 and version
2 is installed in /usr/local/chukwa-2. It is difficult to keep track weather
the symlink should be removed during the upgrade. Hence, the only option is to
manage the symlink removal via a fixed file which will always exist between
different version of the rpm.
/etc/init.d/chukwa-collector is a fixed file which always exist across chukwa
version. The script is changed to detect existence of this file to determine
if the RPM is executed as an uninstall or upgrade. Symlink removal logic will
base on the detection and remove at the right time.
> Create symlink in %file for RPM
> -------------------------------
>
> Key: CHUKWA-211
> URL: https://issues.apache.org/jira/browse/CHUKWA-211
> Project: Hadoop Chukwa
> Issue Type: Improvement
> Components: build and test code
> Affects Versions: 0.1.2
> Environment: Redhat EL 5.1, Java 6
> Reporter: Eric Yang
> Assignee: Eric Yang
> Priority: Blocker
> Fix For: 0.1.2
>
> Attachments: CHUKWA-211.patch
>
>
> For Chukwa 0.1.1.5 release, it used to create /services/chukwa-*/run as
> files. In 0.1.2, this has been changed to use symlink in /services.
> However, the symlink is in %post and %postun. This is a problem for
> upgrading the RPM file. The symlink should be created at build time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
