Changing hatchling shared-data installation directory: /usr/etc -> /etc

2024-03-24 Thread Julian Gilbey
I'm trying to package jupyter-server-terminals, and have hit a snag.
The pyproject.toml file includes the lines:

[tool.hatch.build.targets.wheel.shared-data]
"jupyter-config" = "etc/jupyter/jupyter_server_config.d"

but the resulting file is installed at
/usr/etc/jupyter/jupyter_server_config.d

Now, I can obviously move this to its correct location in debian/rules
(either directly or using an appropriate dh-recognised file in
debian/), but I wonder whether there is a "better" way to do this.  Is
there a way to tell hatchling that shared-data should be installed in
/ rather than in /usr?  Or if I tell hatchling to use / as the base
directory, would that mess everything else up?

I couldn't figure it out from a quick skim of the hatchling docs, so
any thoughts or pointers would be welcome.

Thanks!

   Julian



Re: Changing hatchling shared-data installation directory: /usr/etc -> /etc

2024-03-24 Thread Timo Röhling

Hi Julian,

* Julian Gilbey  [2024-03-24 22:00]:
Now, I can obviously move this to its correct location in 
debian/rules (either directly or using an appropriate dh-recognised 
file in debian/), but I wonder whether there is a "better" way to 
do this.  Is there a way to tell hatchling that shared-data should 
be installed in / rather than in /usr?  Or if I tell hatchling to 
use / as the base directory, would that mess everything else up?
I know that both CMake and Meson special-case sysconfdir to point to 
/etc instead of $prefix/etc when installing to /usr. Hatchling 
should follow their lead.



Cheers
Timo


--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature