[Swift-devel] Issues to resolve for the 0.96 config mechanism

[Mihael Hategan]

Hi,

So, first, when I say "gone" that means "it's not there right now in
trunk". This is work in progress, and I was hoping to get feedback from
everybody, hopefully based on use cases and experiences. This change
brings an opportunity to re-visit some of the things we have and see if
they make sense in the new context and make the right long-term
decisions.

The first question is whether ~/.swift/swift.conf and ./swift.conf
should be explicitly in the search path, since SWIFT_SITE_CONF can do
both:

export SWIFT_SITE_CONF=~/.swift/swift.conf
export SWIFT_SITE_CONF=./swift.conf

Mihael

On Sun, 2014-07-13 at 20:02 -0700, Mihael Hategan wrote:
> Sorry. This discussion went a bit off. I apologize.
> 
> Search path. There are some changes. Here are the details:
> 
> 1. swift/etc/swift.conf is still there
> 2. SWIFT_SITE_CONF is still there. It makes good sense.
> 3. ~/.swift/swift.conf is gone. SWIFT_SITE_CONF does the same and is
> explicit. Can be added back.
> 4. ./swift.conf is gone for reasons of magicality. Can also be added
> back.
> 5. -config on the command line is still there.
> 
> The fundamental difference is that there is no "if it's not there,
> ignore silently and continue" behavior and there is no automated
> chaining. The user has to say what they want. It's a one-time operation
> per file. Very likely less work than the actual contents of the file,
> but less error-prone. It's a choice. That of safety vs. convenience. We
> can bias either way and supplement with tools.
> 
> We could and should discuss the merits of what has changed. It might
> help if we do it one issue at a time.
> 
> Mihael
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel