- From: Daniel DeLeo <
>
- To: Chef <
>
- Subject: [chef-dev] Re: [chef] build omnibus-chef in dedicated dir
- Date: Wed, 19 Nov 2014 08:59:05 -0800
On Wednesday, November 19, 2014 at 7:58 AM, Vasiliy Tolstov wrote:
>
Hello. As i know omnibus-chef have hardcoded paths like /opt/chef/xxx
>
that not very good.
Can you explain why it’s not good?
>
If i send patches for omnibus, omnibus-chef, omnibus-software to get
>
abilit to run something like:
>
>
cd omnibus-chef
>
BUNDLE_PATH=.bundle bundle install --without development
>
BUNDLE_PATH=.bundle bundle exec omnibus build chef -l debug -o
>
base_dir:./local dest_dir:./local/output
You say below that you have a different distro than the ones we already
support. Would it make more sense to always build the packages in this
location on your platform?
>
>
and get in local/output fully working chef that can be dropped to
>
/opt/ and run without problems, does this acceptable by upstream?
This will be really difficult to do. Paths to shared libraries get baked in
to the binaries at compile time.
>
Also if user does not override dest_dir its by fault have value / that
>
mean that current behaviour works fine.
>
What do you think?
>
P.S. I'm need this to properly create archive with chef for my distro.
What distro?
>
>
--
>
Vasiliy Tolstov,
>
e-mail:
>
>
>
(mailto:
)
>
jabber:
>
>
>
(mailto:
)
--
Daniel DeLeo
- [chef-dev] Re: [chef] build omnibus-chef in dedicated dir, Daniel DeLeo, 11/19/2014
Archive powered by MHonArc 2.6.16.