Hi Evans, A +1 for creating symlinks in the post-install phase of the package, since they are needed for the package to work, if I understand correctly. packages itself should work (somehow) out of the box. Why are you not considering packaging the symlinks directly in the RPM/DEB?
Olaf > Am 20.05.2015 um 18:42 schrieb Evans Ye <[email protected]>: > > Hi all, > > I'm just thinking about the following problem and would like to get some > ideas from you experts. > > I notice that the ignite-hadoop package needs to rely on puppet recipes to > symlik needed jars into /usr/lib/hadoop/lib, otherwise no mapreduce job > can be ran w/ ignite hadoop accelerator. > However, there might be a case that users are not using bigtop puppet, or, > sometimes users only need to quickly obtain an environment with specific > components installed and running. In that case, installing bigtop provided > package might be the easiest way. Take RPM packaging as an example, what do > you think if we can do symlink at the post-install phase of RPMs so that > the package can start working functionally right after it is installed? > > Thanks, > Evans
signature.asc
Description: Message signed with OpenPGP using GPGMail
