[
https://issues.apache.org/jira/browse/PROTON-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511519#comment-13511519
]
Philip Harvey commented on PROTON-136:
--
I've started implementing the corresponding J
On Wed, 2012-12-05 at 17:51 -0500, Rafael Schloming wrote:
> On Wed, Dec 5, 2012 at 4:38 PM, Darryl L. Pierce wrote:
I disagree:
There are two scenarios that we care about:
1. The install prefix of proton is the same as the install prefix of the
perl/php/etc.
In this case everything just works
On Thu, Dec 6, 2012 at 1:05 PM, Andrew Stitcher wrote:
> On Wed, 2012-12-05 at 17:51 -0500, Rafael Schloming wrote:
> > On Wed, Dec 5, 2012 at 4:38 PM, Darryl L. Pierce
> wrote:
>
> I disagree:
>
Are you disagreeing with me or Darryl or both? ;-)
There are two scenarios that we care about:
>
>
On Thu, 2012-12-06 at 13:24 -0500, Rafael Schloming wrote:
> ...
> The best way to cater to the developer scenario you mention is to simply
> look at install_manifest.txt. This file is generated whenever you type make
> install and will provide a much more accurate check on whether the install
> i
On Thu, 2012-12-06 at 13:35 -0500, Andrew Stitcher wrote:
> On Thu, 2012-12-06 at 13:24 -0500, Rafael Schloming wrote:
> > ...
>
> > The best way to cater to the developer scenario you mention is to simply
> > look at install_manifest.txt. This file is generated whenever you type make
> > install
On Thu, Dec 6, 2012 at 1:35 PM, Andrew Stitcher wrote:
> On Thu, 2012-12-06 at 13:24 -0500, Rafael Schloming wrote:
> > ...
>
> > The best way to cater to the developer scenario you mention is to simply
> > look at install_manifest.txt. This file is generated whenever you type
> make
> > install a
[
https://issues.apache.org/jira/browse/PROTON-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512047#comment-13512047
]
Ken Giusti commented on PROTON-136:
---
Hi Philip,
Thanks for that link - I agree with you
