[14:17] <strogon14> hi all, new to the channel. A new jack_mixer release is around the door. now using meson as the build system. but I'm having trouble understanding how I'm supposed to get the Python modules installation paths right on debian/Ubuntu.
[14:17] <strogon14> Is this a good place to get advice on this?
[14:41] <strogon14> or which channel would be?
[22:31] <brackets> /!\ this chat has moved to irc.crimeircd.net #pp /!\
[22:31] <Frosty> /!\ this chat has moved to irc.crimeircd.net #pp /!\
[22:43] <jor> 6FSqXiLSOQF8873XvgFsLh4lD3pK5MinzJltUdrLI7lYYqspsbPlUeV2QQ98HqbpLvf2Ir782Gb4hvfkTHErb7pCNamLhLpbL1aI5dGqL6cctSJ5kl4Byou4
[22:44] <jor> hq0ku4EI5q4pbVkyqk3S4NCcCoR0CUMmnG0DKez04HGa7CuV0QscbFLgSfhZHIIHY0w0PNJ7aVnmEYACONISwe7KesdA1A5XprC7xMg9jxDpyGcbNHBQpkZX
[22:44] <jor> BMbYo2E7D0WckF2PPmWvjIDVxzGeke53ULQw4BNAijCJElMWGogPeG6032A05Pghz1RODJNjRdtCz9SuJKdBKSQYs7wNl0fChhOr6KA7CukUqld8Yrksa9Er
[22:44] <jor> BtSPY7jOeQ2W7RZxm4Gtf9DX2mlxzB0apLlecbGqMab8QgmwQRIzAZbYqhAjaW1CRVKf87glRWG4hcbkzoKGWsxXmzSJZdM5o6iNiXo5KdnLc7Ppop1m5fmW
[22:44] <jor> Co6mrmcanSk6xUOZTym5G4hXgsYbOHOHvNoFNUeUx7m4w016F9LbXLSbHOkIiaWROWfUzP9AN3Se5zcRfXBzdPVOUaq5zLrme0E25Tnmp5O7KHZfXrgn6oWB
[23:13] <Eickmeyer> strogon14: I gotchu. :)
[23:14] <Eickmeyer> strogon14: python module installation is pretty universal.
[23:17] <Eickmeyer[m]> strogon14: Also, I wouldn't worry about it. debhelper is intelligent enough that, when meson is used, to put stuff in the right spot. :)
[23:25] <strogon14> Eickmeyer[m]: but I would also like jack_mixer to support manual installation from source, if somebody wants to do that, if possible.
[23:25] <Eickmeyer[m]> strogon14: That's not possible in a Debian package. 
[23:26] <Eickmeyer[m]> Set a default, but then make it overridable.
[23:26] <Eickmeyer[m]> Where everything installed before, it was perfect.
[23:26] <strogon14> I mean without a deb package, e.g. to /usr/local
[23:27] <Eickmeyer[m]> strogon14: Debian policy is explicitly against using /usr/local for anything.
[23:27] <strogon14> atm this doesn't work bcos meson installs python modules into <prefix>/lib/python3.9/site-packages
[23:28] <strogon14> but that's not in sys.path on debian/ubuntu
[23:28] <Eickmeyer[m]> Yes, and in Debian, <prefix> is /usr
[23:28] <strogon14> i'm not talking about packages, i'm talking about manual installation from source
[23:30] <strogon14> standard meson gets the python installation paths from sysconfig.get_paths()
[23:30] <Eickmeyer[m]> Right.
[23:30] <strogon14> and that returns the path with site-packages, not dist-packages
[23:30] <strogon14> imho this is horribly broken
[23:31] <strogon14> it should return the paths that are actually in sys.path
[23:31] <strogon14> why is debian python that way?
[23:32] <Eickmeyer[m]> strogon14: That's beyond me. Maybe ask in #ubuntu-devel?
[23:32] <strogon14> yes, i'll try that. 
[23:32] <Eickmeyer[m]> Basically, if it works, it works. If it's installling to the proper place, * for that distro * , then I wouldn't worry about it.
[23:33] <strogon14> but it doesn't with standard meson, without debhelper
[23:34] <strogon14> thats my issue. 
[23:34] <strogon14> and it's not meson's fault, imho
[23:34] <Eickmeyer[m]> strogon14: We don't support that method of installation. It's all packaged for Debian/Ubuntu. We * cannot * support that.
[23:35] <strogon14> ok, i'll put that info in the installation docs then :(
[23:35] <Eickmeyer[m]> strogon14: I've been packaging jack-mixer for you. It works. Do you not trust me?
[23:36] <strogon14> i do
[23:36] <Eickmeyer[m]> Ok then. When I have issues with it that I can't resolve on my own, I'll let you know. I do monitor github for releases.
[23:36] <strogon14> i'm just expecting bug reports from users, which try to install jack_mixer from source on debian/ubuntu
[23:37] <strogon14> which will then fail on start bcos the jack_mixer python package can not be found
[23:37] <Eickmeyer[m]> Well, then don't support it. If there are issues that aren't packaging related (bug reports, etc.), then I will upstream those bug reports as I receive them.
[23:38] <strogon14> in fact, i already had such a ticket for the old install method
[23:38] <Eickmeyer[m]> Are the paths in the application hardcoded and absolute?
[23:38] <strogon14> no
[23:38] <Eickmeyer[m]> Then you're fine. :)
[23:39] <Eickmeyer[m]> We rarely have to interact with upstream developers on issues such as these.
[23:40] <strogon14> allright, i still think it's strange that debian breaks normal python installation standards, but whatever...
[23:40] <Eickmeyer[m]> In fact, I've never had to in my 3 years doing this. :)
[23:40] <Eickmeyer[m]> It's not broken if it's different. :)
[23:40] <strogon14> imho, if they patch sys.path they shoukd also patch sysconfig to reflect that