[
https://issues.apache.org/jira/browse/TS-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157276#comment-15157276
]
ASF GitHub Bot commented on TS-4048:
------------------------------------
Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/490#issuecomment-187268952
> Yeah i know what you mean about that patch series... working on it
thanks :)
> I just checked for configure to run in default configuration when looking
for those dependencies
> trying to keep the images small.
>
> I can add those optional dependencies as well. Would be great if they
were documented as optional
> though (doclink).
>
> What do you think about dependencies for plugins? Shall they be added as
well?
The original goal of these was so that dev could spin up build environments
for configurations they didn't have easy access to, which meant that I
installed all the dependencies to build all the optional components. If you can
get all the dependencies in, that would be great. On RHEL-based systems I
remember it was a bit tedious to get the right dependencies out of EPEL though.
> That FreeBSD image is gone and there wasn't any provisioning at all so
that probably never worked
> ootb anyways. If that's still needed i'll try to add it as well but i'd
prefer to do that after all the other stuff
> is working again.
No that's fine; I just wanted to check whether this was a deliberate
decision. A FreeBSD image will just bitrot again unless there's someone to take
care of it.
> Broken Vagrantfile in a lot of ways
> -----------------------------------
>
> Key: TS-4048
> URL: https://issues.apache.org/jira/browse/TS-4048
> Project: Traffic Server
> Issue Type: Bug
> Components: Build, Tools
> Reporter: Christoph Keller
> Priority: Minor
> Fix For: sometime
>
>
> The Vagrant-File seems to be broken.
> 1. I tried to "vagrant up centos64" which failed due to files that could not
> be downloaded during provisioning.
> 2. Saucy Images are no longer available and should be removed from
> Vagrantfile.
> 3. I guess it would be better to use sshfs instead of nfs for the shared
> folder due to the fact that a lot of people use encrypted home-directories
> these days which makes mounting the shared folder fail. You don't even get a
> proper errormessage for that.
> I didn't check all resources refered to by either Vagrantfile or the puppet
> files but i guess there are even more broken links.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)