Local tool configuration


(Paulo Faria) #1

Daniel, could please elaborate why you think the flags shouldn’t be on the manifest?
Also, you think it shouldn’t be there for now or never?


(Daniel Dunbar) #2

Daniel, could please elaborate why you think the flags shouldn’t be on the manifest?
Also, you think it shouldn’t be there for now or never?

Two reasons:

1. Yes, some things should be in the manifest, but designing the exact manifest syntax is much more subtle (and we don't want it to be a grab bag like "any list of flags"). Adding the local config doesn't have to be at the same standard though, since it doesn't propagate.

2. There will always be other kinds of things which are possibly shared and change the behavior of the command line tool, but don't relate to the nature of the package. I don't think those belong in the manifest. As a silly example, suppose the tool had some kind of "auto update" behavior that the package developers wanted to enable -- that might go in the config, but it isn't part of the manifest. We don't have any examples currently, but I think more will come along, so I'm not really worried about the file "living on".

- Daniel

···

On Nov 11, 2016, at 11:09 AM, Paulo Faria via swift-build-dev <swift-build-dev@swift.org> wrote:

_______________________________________________
swift-build-dev mailing list
swift-build-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-build-dev