Matt Madia wrote:
Wouldn't it make sense to take the tactic that, if it is included for BeOS compatibility, that activating it by default makes the same sense as inclusion. Why add a additional step ? There is no downside to the activation of the package, it is already using disk space.On 10/18/13, Giovanni Mugnai <musical777@xxxxxxxxx> wrote:And as my reply said, i made a workaround, which works like the old optional package "BeOSCompatibility - creates links within the system to support old apps"....So, to ensure the functionality of these old apps on the "new" Haiku (and offers to new users the ability to immediately download and install an app - i'm also making hpkgs of old apps), could be the case to make an official package which make legacy links, like the old "BeOSCompatibility" optional package?Could you attach that package to a new ticket? Perhaps such a package could be included (but not activated) by default. --mmadia
Sean