bengalih
Senior Member
I've got a question/topic for discussion that is interesting to/bothering me:
Why does Entware co-opt the entire "/opt" folder, being that it is just a single software package (albeit a repo for multiple packages)?
From my time working with traditional unix systems, "/opt" has always been the directory/mount point for 3rd party software packages. While Entware certainly would fall into this category, I would expect to find it at "/opt/entware" and not have "/opt" be a link directly into the entware folder.
A user/admin may wish to install another package outside of entware onto their system and the usual place for this would be /opt. On an asuswrt-merlin install (with entware) this would place that package within the entware structure, which is just mucky. If one were to wipe-out (or simply want to back-up) their entware install, this 3rd party package is now at risk of being removed and/or included when the intent was not to do so.
I would think it would have been closer to unix standards to link /opt either to the entire flash drive or at least to an /opt folder within it where Entware would be installed. Then, instead of there being years and years of development with things pointing just to "/opt", they would be pointing to "/opt/entware" instead.
Was this just a bad decision back at the very beginning and now it is too hard to fix? Or is there some better explanation of why it was done this way.
It is unclear to me at this point who is actually responsible for Entware, as the github page redirects all requests back to platform specific pages like here. So, I don't know if @RMerlin is the correct person to address this, or if there is a better place I can ask this question.
I had asked about this in @thelonelycoder Diversion thread, and got some feedback, but I don't think continuing in that thread is conducive to getting the answers I'm looking for.
Would appreciate any feedback on the "why" without simply being told "well that's the way it is."
Why does Entware co-opt the entire "/opt" folder, being that it is just a single software package (albeit a repo for multiple packages)?
From my time working with traditional unix systems, "/opt" has always been the directory/mount point for 3rd party software packages. While Entware certainly would fall into this category, I would expect to find it at "/opt/entware" and not have "/opt" be a link directly into the entware folder.
A user/admin may wish to install another package outside of entware onto their system and the usual place for this would be /opt. On an asuswrt-merlin install (with entware) this would place that package within the entware structure, which is just mucky. If one were to wipe-out (or simply want to back-up) their entware install, this 3rd party package is now at risk of being removed and/or included when the intent was not to do so.
I would think it would have been closer to unix standards to link /opt either to the entire flash drive or at least to an /opt folder within it where Entware would be installed. Then, instead of there being years and years of development with things pointing just to "/opt", they would be pointing to "/opt/entware" instead.
Was this just a bad decision back at the very beginning and now it is too hard to fix? Or is there some better explanation of why it was done this way.
It is unclear to me at this point who is actually responsible for Entware, as the github page redirects all requests back to platform specific pages like here. So, I don't know if @RMerlin is the correct person to address this, or if there is a better place I can ask this question.
I had asked about this in @thelonelycoder Diversion thread, and got some feedback, but I don't think continuing in that thread is conducive to getting the answers I'm looking for.
Would appreciate any feedback on the "why" without simply being told "well that's the way it is."