mbox series

[bug#69023,v2,0/5] gnu: bqn: Update cbqn.

Message ID cover.1714438234.git.aecepoglu@fastmail.fm
Headers show
Series gnu: bqn: Update cbqn. | expand

Message

aecepoglu April 30, 2024, 12:50 a.m. UTC 
Applied feedback received.

I am not sure on how to package Singeli differently. It's a directory tree of BQN code that the author would like to think is a library. I think it functions better as an executable, one that relies on BQN itself.
Is this an issue we can revisit later?

Let me know how to proceed.

aecepoglu (5):
  gnu: bqn: Add singeli.
  gnu: bqn: Update dbqn.
  gnu: bqn: Update bqn-sources.
  gnu: bqn: Update cbqn-bootstrap.
  gnu: bqn: Update cbqn.

 gnu/packages/bqn.scm | 176 ++++++++++++++++++++++++++-----------------
 1 file changed, 107 insertions(+), 69 deletions(-)


base-commit: b64862e5cb8209c92aa2eff4cec0be328e38c45d

Comments

Liliana Marie Prikler April 30, 2024, 4:55 a.m. UTC | #1 
Am Dienstag, dem 30.04.2024 um 01:50 +0100 schrieb aecepoglu:
> Applied feedback received.
> 
> I am not sure on how to package Singeli differently. It's a directory
> tree of BQN code that the author would like to think is a library. I
> think it functions better as an executable, one that relies on BQN
> itself.
> Is this an issue we can revisit later?
I would also like to have it as an executable relying on BQN.  There's
a few things you can do if you need them for bootstrapping.  You could
for example take (package-source singeli) as an input where only the
sources are required.

For packaging singeli itself; assuming you don't need to AOT-compile,
I'd suggest you go with a plan along the lines of

singeli → bin (don't forget to wrap-program)
include → include/singeli
doc → doc/singeli
data → share/singeli
*.bqn → lib/bqn

The singeli bin is possibly somewhat special, as you need to also
supply bqn.  Not sure what the smartest move here is; I'd personally
try to use $(which bqn) with a fallback to a known good one.

Cheers