From stegeman at gmail.com Sat Nov 1 00:02:36 2014 From: stegeman at gmail.com (Luite Stegeman) Date: Sat, 1 Nov 2014 01:02:36 +0100 Subject: New fields/flags and semantics for GHCJS In-Reply-To: References: Message-ID: One more thing I had forgotten to mention, and still need to implement in GHCJS: If a library has web assets, for example CSS files or images for a GUI framework library, they should be listed under `data-files` of a package. The compiler then makes all data directories of dependencies available in a subdirectory of the directory containing the generated JavaScript and HTML files. Libraries then use their own "Paths_packagename" module to find the location. Location should probably be based on the package key, not the package version, so this requires #2194 to be resolved first. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sven.heyll at gmail.com Sun Nov 2 11:26:19 2014 From: sven.heyll at gmail.com (Sven Heyll) Date: Sun, 2 Nov 2014 12:26:19 +0100 Subject: Where to put these flags? Message-ID: Hi List I am currently adding cabal-install flags tell cabal-install how to compile the setup program (in case the "external method" is used. Now what should I do? Should I ... a) extend global flags? b) extend only ConfigExFlags? (which means users cannot cross-compile without explicitly calling 'configure', OTOH users can set these values in cabal config file) c) continue to add a set of flags to every command? My preferences: (b) > (c) > (a). What do you think? With best regards Sven Heyll -------------- next part -------------- An HTML attachment was scrubbed... URL: From the.dead.shall.rise at gmail.com Sun Nov 2 11:47:01 2014 From: the.dead.shall.rise at gmail.com (Mikhail Glushenkov) Date: Sun, 2 Nov 2014 12:47:01 +0100 Subject: Where to put these flags? In-Reply-To: References: Message-ID: Hi, On 2 November 2014 12:26, Sven Heyll wrote: > a) extend global flags? > b) extend only ConfigExFlags? > (which means users cannot cross-compile without explicitly calling > 'configure', OTOH users can set these values in cabal config file) > c) continue to add a set of flags to every command? > > My preferences: (b) > (c) > (a). +1 for option b. Since build/test/... now call 'configure' automatically, they will probably be extended to accept configure flags at some point. From lsp at informatik.uni-kiel.de Mon Nov 17 23:31:37 2014 From: lsp at informatik.uni-kiel.de (lennart spitzner) Date: Tue, 18 Nov 2014 00:31:37 +0100 Subject: feedback for changes to the commandline documentation/help, please Message-ID: <546A8559.9020904@informatik.uni-kiel.de> https://gist.github.com/lspitzner/36321a9f074cb9b897ac or is there a better process? should i pull-request or open a ticket? Lennart From the.dead.shall.rise at gmail.com Tue Nov 18 23:18:01 2014 From: the.dead.shall.rise at gmail.com (Mikhail Glushenkov) Date: Wed, 19 Nov 2014 00:18:01 +0100 Subject: feedback for changes to the commandline documentation/help, please In-Reply-To: <546A8559.9020904@informatik.uni-kiel.de> References: <546A8559.9020904@informatik.uni-kiel.de> Message-ID: Hi, On 18 November 2014 00:31, lennart spitzner wrote: > https://gist.github.com/lspitzner/36321a9f074cb9b897ac Looks good after a cursory review. Regarding your questions: > does cabal freeze really overwrite any existing cabal.config? Not sure (I don't use 'freeze' much). You can always test/look at code. > for test/bench command: What exactly was meant by "configure with UserHooks"? did i represent that correctly in the description? This is refers to writing custom Setup.hs scripts. Users can change the UserHooks record they supply to Cabal. > suggestions for sandbox init description? it might be imprecise atm. Looks OK to me. > is there a notable difference between cabal sandbox hc-pkg and cabal exec -- ghc-pkg? The former uses the compiler the package was configured with, while the latter uses the one in PATH. > or is there a better process? should i pull-request or open a ticket? Yes, if you think that your changes are ready to be merged, please send a pull request.