On Wed, Jun 10, 2015 at 02:39PM, Evans Ye wrote: > Yes, that's what I was thinking. If we decide to leverage puppet recipes to > complete the setup after packages are installed, then those packages can > only be deployed by bigtop puppet instead of doing "yum install" or > "apt-get install", which limited the usage of bigtop packages. It's fine to > leave configurations for users but I think we better have symlink installed > within package installation. :)
My only concern with this if that's an ok practice from the the linux packaging guidelines point of view (if such think indeed exists). Otherwise, I am for the simplification of the deployment. Cos > 2015-06-07 4:54 GMT+08:00 Olaf Flebbe <o...@oflebbe.de>: > > > 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 <evan...@apache.org>: > > > > > > 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 > > > >
