Replace lockfile format with JSON? about paket

[forki]

actually I'm very happy with format. It's exactly the same as bundler

[forki]

/cc @agross

[agross]

I have to admit I like the readability of the current format. Simple, no distractions like braces to satisfy a tool.

Alex

Alexander Groß
Tiny phone, tiny mail

On Thu, Sep 4, 2014 at 7:03 PM, Steffen Forkmann [email protected]
wrote:

/cc @agross

Reply to this email directly or view it on GitHub:
#53 (comment)

[isaacabraham]

Yeah, true - my thinking is more around whether this is file designed to be read / written by people first and foremost (as is the case with the packages.fsx) or by Paket.exe? If the former - definitely makes sense to keep as is. If the latter - maybe not.

[forki]

It's meant to be read by people. You will always cross check before commit.
On Sep 4, 2014 7:32 PM, "Isaac Abraham" [email protected] wrote:

Yeah, true - my thinking is more around whether this is file designed to
be read / written by people first and foremost (as is the case with the
packages.fsx) or by Paket.exe? If the former - definitely makes sense to
keep as is. If the latter - maybe not.

—
Reply to this email directly or view it on GitHub
#53 (comment).

[agross]

👍, I read it all the time to reason about paket's computation results.

[isaacabraham]

Closing :-)

[isaacabraham]

@forki Question - if the whole point of paket is to abstract users away from uber dependency chains - why would you cross check before commit?

[forki]

We want to make it super clear for the user to see what happens in his
solution.
We don't want to free him from dependency management.
On Sep 4, 2014 7:53 PM, "Isaac Abraham" [email protected] wrote:

@forki https://github.com/forki Question - if the whole point of packet
is to abstract users away from uber dependency chains - why would you cross
check before commit?

—
Reply to this email directly or view it on GitHub
#53 (comment).