Rich Freeman wrote: > >> I personally find it annoying when people fork projects, decide not to > >> maintain ABI compatibility with the original project, and then keep > >> filenames the same/etc such that the packages collide in their > >> recommended configurations. > > > > Some people do it on purpose, with the outspoken goal of doing > > maximum harm to the original project and lock users into the fork. > > In such cases it probably would be helpful if distros talked to each > other and agreed to hack the build so that the new files would not > collide.
Yes, I think that would be very helpful. Unfortunately, my experience is that package maintainers in (all!) distros either buy into convenient but wholly untrue propaganda or simply settle for doing the same as "everyone else". > That then leaves the upstream package with two choices - keep their > build the same so that anybody who uses it to develop against their > library ends up with a build that doesn't work on any actual distro, > or play nice. That is sadly a unicorn. > A NyxOS-like approach where you just prefix EVERYTHING on the system > might also work. Yes, this is an interesting idea, and a good way to shield users from evil. > there wouldn't be an /etc/init.d, but rather a bazillion > /pkg/guid/etc/init.d directories or something like that I guess an abstraction akin to pkg-config could solve the problem. //Peter
