On 15/05/2015 22:42, Pete Goodeve wrote:
OK. You've been asking for examples of why the read-only hierarchy
and the removal of common breaks things. Here's one, that has me
fairl y firmly blocked at the moment.
I make extensive use of Ruby, and have a number of libraries of
my own that are used by my apps. The Ruby standard is that
they should go in .../lib/ruby/site-ruby, but under PM this is
installed in /boot/system/lib and is read-only! Ruby does not
know about the 'non-packaged' tree.
As I've still been mostly using my pre-PM system (:-/) -- with
the libraries in /boot/common -- it hasn't hit me 'til now, but I've
just been making an effort to get everything working in hrev49167,
and this has brought me up short.
It is not appropriate to put these libraries in packages,
because they are always in flux. I need to be able to edit them
quickly and in place.
So what to do?
