12:40 <adamcstephens> ifreund: In nixpkgs we have a few different ways to handle a rename, so river -> river-classic is easy. The thing that won’t work so well is then attempting to reuse the name river for non-classic if we’re going to package that. I’m not sure there’s a good option for this. Reusing the name will break the rename redirects.

12:46 <ifreund> adamcstephens: replacing specific versions isn't supported?

12:46 <ifreund> I'd expect a feature that replaces specifically river versions less than 0.4.0 with river-classic

12:57 <adamcstephens> No because versions are tied to commits in the git tree. A user asks for river from a nixpkgs git commit, not a specific version of river itself.

13:03 <ifreund> hmm, I think I see

13:04 <ifreund> well, I probably need to implement some kind of deprecation message anyways telling people to switch to river-classic manually

13:05 <ifreund> and river 0.4.0 could refuse to start and print a "consider switching to river-classic" message if a -wm option isn't passed

13:05 <ifreund> suggestions welcome

13:05 <adamcstephens> That would help. I can rename to classic as soon as next release, and then when rwm is released if it has a message then people would understand they need to act. Unfortunately people wait long periods between updating their systems

13:05 <revsuine> Could perhaps the river-classic rename happen before 0.4.0 is released, so that everyone using river just switches to classic, and then if someone wants to switch to 0.4.0 they can manually install the `river` package again once it's out?

13:06 <revsuine> so there's no "conflicting" `river` package in the 0.4.0 release for a while

13:06 <ifreund> revsuine: yes, exactly that is the plan

13:07 <ifreund> I do realize that the least breaking way to do would be to just release the widly breaking river 0.4.0 under a name that's not river

13:07 <ifreund> but I like the name river

14:28 <revsuine> Is it possible to get the tags of the focused view using the River protocols? I'm reading through now and I can see view_tags in zriver_output_status_v1 to get an array of view tags, and focused_view in zriver_seat_status_v1 to get the *title* of the focused view, but I don't know how I'd translate that to the array index of the focused view from view_tags?

15:01 <ifreund> revsuine: don't think so, the 0.3.x protocols are really quite limited unfortunately

15:01 <ifreund> which is why I've decided to take the current direction with the river window management protocol

15:11 <revsuine> ifreund: ah that's a real shame—I can't be the only one who wants to do particular operations on the tag bitfield of the current focused view. Maybe time to look into 0.4.0 then and figure out how to write the behaviour I want with a River window manager 😅

15:54 <hrushw> exit

16:37 <mekeor> i'd vote for a more metaphorical, maybe funny name instead of "river-classic" that plays with the "river" meaning. perhaps "beaver" because beavers try to stop the flow of rivers (or time, like lazy computer users), leading to a dam, and leading to the river to change its way, like a spin-off / fork ... :D

16:56 <FireFly> cute as it might be, that'd probably just lead to a lot more confusion