alpine already merged support for /usr/libexec/rc onto abuild, yay
still a bit anxious, specially if we end up renaming stuff to /openrc, now that $libexec/rc and /etc/rc are somewhat public ($libexec/rc already existed but it was fully internal)
it's probably not that big of a deal if a year or more from now we change that, keep the old paths around, etc
but bweeh the anxiety
one day i'm not gonna be so anxious about stuff, one day
still a bit anxious, specially if we end up renaming stuff to /openrc, now that $libexec/rc and /etc/rc are somewhat public ($libexec/rc already existed but it was fully internal)
it's probably not that big of a deal if a year or more from now we change that, keep the old paths around, etc
but bweeh the anxiety
one day i'm not gonna be so anxious about stuff, one day
@navi could always have a migration thingy which moves it from one to the other
@solonovamax i dunno if openrc messing with package manage'd files in /usr is a good idea at all
specially since immutable systems with ro /usr are a thing now
specially since immutable systems with ro /usr are a thing now
@navi hmmm, that's true
if you decide to move, then you could always do like fallback + warning
e.g. first check [...]/openrc, if it isn't there then check [...]/rc. if the second one is there, emit a warning saying "this will stop working in version a.c.b, please move your config" and then give distro maintainers a heads up
@solonovamax fallback works, warning would be tricky, as the code works with both the hardcoded list, and with the RC_PATH environment variable
I think renaming would be ok if there is no alpine stable release with packaged files there (and as mentiond we can't really move the files)
@sertonix by the time we get to renaming, i think there would be -- if not on alpine, on gentoo or pmos or debian (debian specially, as they were really waiting for RC_PATH)
so if a rename were to happen, it'd have to be the traditional "add new entries, keep old ones until all packages have had a bump using new location, likely years"
plus well, the last, laaast, thing i need rn is time pressure to making the choice of rename or not :/
so if a rename were to happen, it'd have to be the traditional "add new entries, keep old ones until all packages have had a bump using new location, likely years"
plus well, the last, laaast, thing i need rn is time pressure to making the choice of rename or not :/