Newest at the top
2025-07-24 21:20:19 +0200 | Guest96 | (~Guest96@81-207-104-14.fixed.kpn.net) |
2025-07-24 21:17:16 +0200 | caubert | (~caubert@user/caubert) caubert |
2025-07-24 21:16:39 +0200 | LainIwakura | (~LainIwaku@user/LainIwakura) (Quit: Client closed) |
2025-07-24 21:15:56 +0200 | <sm> | https://hackage.haskell.org/package/base-4.21.0.0/docs/System-Environment.html#v:getExecutablePath or something |
2025-07-24 21:13:29 +0200 | <sm> | can you use the standard tricks shell scripts use to find their file location ? Analyse the command line, etc ? |
2025-07-24 21:12:28 +0200 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 240 seconds) |
2025-07-24 21:11:46 +0200 | sord937 | (~sord937@gateway/tor-sasl/sord937) (Quit: sord937) |
2025-07-24 21:09:19 +0200 | manwithluck | (~manwithlu@2a09:bac1:5bc0:20::39b:8b) manwithluck |
2025-07-24 21:09:08 +0200 | sprotte24 | (~sprotte24@p200300d16f056400b9509f58729e6016.dip0.t-ipconnect.de) |
2025-07-24 21:08:34 +0200 | manwithluck | (~manwithlu@2a09:bac1:5bc0:20::39b:8b) (Ping timeout: 260 seconds) |
2025-07-24 21:04:37 +0200 | fp | (~Thunderbi@89-27-10-140.bb.dnainternet.fi) fp |
2025-07-24 21:04:13 +0200 | <dminuoso> | __monty__: Is this some internal work tool or something you want to share publically? |
2025-07-24 21:03:51 +0200 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
2025-07-24 21:00:44 +0200 | caconym74 | (~caconym@user/caconym) caconym |
2025-07-24 21:00:03 +0200 | caconym74 | (~caconym@user/caconym) (Quit: bye) |
2025-07-24 20:57:46 +0200 | caubert | (~caubert@user/caubert) (Ping timeout: 276 seconds) |
2025-07-24 20:56:27 +0200 | rvalue- | rvalue |
2025-07-24 20:55:39 +0200 | LainIwakura | (~LainIwaku@user/LainIwakura) LainIwakura |
2025-07-24 20:53:13 +0200 | jespada | (~jespada@2800:a4:2291:9400:14c2:89da:d45:6f6a) (Ping timeout: 276 seconds) |
2025-07-24 20:52:36 +0200 | <__monty__> | sm: While that technically works I'm looking for a less chaotic method, it's already a lot of juggling of formats and templates. |
2025-07-24 20:52:29 +0200 | rvalue | (~rvalue@about/hackers/rvalue) (Ping timeout: 240 seconds) |
2025-07-24 20:52:24 +0200 | caubert | (~caubert@user/caubert) caubert |
2025-07-24 20:52:04 +0200 | manwithluck | (~manwithlu@2a09:bac1:5bc0:20::39b:8b) manwithluck |
2025-07-24 20:51:44 +0200 | rvalue- | (~rvalue@about/hackers/rvalue) rvalue |
2025-07-24 20:51:21 +0200 | manwithluck | (~manwithlu@2a09:bac1:5bc0:20::39b:8b) (Ping timeout: 276 seconds) |
2025-07-24 20:50:15 +0200 | <__monty__> | dminuoso: Sure. This is somewhat me poking at Shake and seeing how close to a make(1) replacement it can be. |
2025-07-24 20:48:44 +0200 | LainIwakura | (~LainIwaku@user/LainIwakura) (Quit: Client closed) |
2025-07-24 20:47:35 +0200 | Digitteknohippie | Digit |
2025-07-24 20:34:05 +0200 | <dminuoso> | __monty__: So the "installation method" is to do `git clone`? |
2025-07-24 20:33:20 +0200 | <sm> | __monty__ you could embed those files in the script, and if needed, write them out to a temp file or known directory at runtime |
2025-07-24 20:32:46 +0200 | trickard__ | trickard |
2025-07-24 20:32:45 +0200 | trickard | (~trickard@cpe-50-98-47-163.wireline.com.au) (Ping timeout: 252 seconds) |
2025-07-24 20:32:38 +0200 | Square2 | (~Square@user/square) Square |
2025-07-24 20:31:40 +0200 | trickard__ | (~trickard@cpe-62-98-47-163.wireline.com.au) |
2025-07-24 20:31:09 +0200 | target_i | (~target_i@user/target-i/x-6023099) target_i |
2025-07-24 20:28:06 +0200 | <__monty__> | But my currently desired way of packaging this is to have it all in the project directory. |
2025-07-24 20:27:34 +0200 | <dolio> | Well, not completely cleanly, but none of the warnings seem to cause errors. |
2025-07-24 20:27:28 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 240 seconds) |
2025-07-24 20:26:43 +0200 | <dolio> | glguy: Yeah, that builds cleanly here, too. |
2025-07-24 20:26:26 +0200 | <dminuoso> | Unless you include into the object files via TH. |
2025-07-24 20:26:15 +0200 | <dminuoso> | The moment you start adding non-code assets, you're already in "how do I package/ship this" territory. |
2025-07-24 20:25:52 +0200 | <dminuoso> | Well, with source-translated languages, I feel it is our obligation to provide one or more packaging/installation methods that cover these concerns.. |
2025-07-24 20:25:01 +0200 | <__monty__> | So it has the same problem Paths_pkgname modules have, it doesn't help in the absence of cabal-install. |
2025-07-24 20:24:42 +0200 | caubert | (~caubert@user/caubert) (Ping timeout: 276 seconds) |
2025-07-24 20:24:21 +0200 | Frostillicus | (~Frostilli@2600:380:5a56:e60:91c0:c8fc:8c13:b464) (Read error: Connection reset by peer) |
2025-07-24 20:23:50 +0200 | <dminuoso> | Yes. |
2025-07-24 20:23:31 +0200 | <__monty__> | dminuoso: That's another Cabal option, no? |
2025-07-24 20:22:39 +0200 | <dminuoso> | __monty__: extra-source-files perhaps? |
2025-07-24 20:21:57 +0200 | <__monty__> | dminuoso: In this case it's Dhall files (the types for the configuration the user can pass in) and Latex files (templates that are filled in from said configuration). |
2025-07-24 20:21:13 +0200 | manwithluck | (~manwithlu@2a09:bac1:5bc0:20::39b:8b) manwithluck |