09-03-2015, 10:50 AM
For a user there is no difference. He installs a program and one additional .hpkg is installed.
He gets some extra stuff, but nothing is linked into the applications menu from the yab.hpkg. As far as user experiance goes, there is no difference between installing yab or installing libyab.so.
He does get the extra benefit of being able to run a yab script without needing to install another .hpkg.
At this point, re-thinking the issue, I see no reason to have a libyab .hpkg.
If there is a real issue with the current packaging that actually impacts the user or usability, I will change my position, but just to make the user feel that his program is a real program doesn't convince me.
He gets some extra stuff, but nothing is linked into the applications menu from the yab.hpkg. As far as user experiance goes, there is no difference between installing yab or installing libyab.so.
He does get the extra benefit of being able to run a yab script without needing to install another .hpkg.
At this point, re-thinking the issue, I see no reason to have a libyab .hpkg.
If there is a real issue with the current packaging that actually impacts the user or usability, I will change my position, but just to make the user feel that his program is a real program doesn't convince me.
