#9584 closed bug (fixed)
installoptionalpackage beoscompatibility gives error
Reported by: | Kev | Owned by: | mmadia |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Build System | Version: | R1/alpha4.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
/> installoptionalpackage beoscompatibility To be installed: BeOSCompatibility Warning: Adding BeOS compatibility symlinks. This will go away. Please fix your apps! /boot/common/cache/tmp/install-optpkg.sh: line 286: AddDirectoryToHaikuImage: command not found Generating a list of Package Names ... ... done. />
Did it actually install?
This is on hrev45413 gcc4hybrid.
Change History (11)
comment:1 by , 12 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 12 years ago
Thanks, I understood the warning. What I wasn't sure about was:
AddDirectoryToHaikuImage: command not found
comment:3 by , 12 years ago
Ah, didn't see that. Then no, it wasn't installed properly. However, installoptionalpackage is basically just a shell script hack that can only handle a subset of the full list of build-time optional packages, i.e. the ones that just unzip a file. More complex ones that use other jam directives can't be handled by it, such as this one and the Development packages. That's not realistically something that will be fixed since it will be superseded by the actual package management anyways.
comment:4 by , 12 years ago
At the very least, Matt could blacklist this package from the script if he doesn't have motivation to support the AddDirectoryToHaikuImage rule.
comment:5 by , 12 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
comment:6 by , 12 years ago
Owner: | changed from | to
---|---|
Status: | reopened → in-progress |
It'll be easy enough to implement AddDirectoryToHaikuImage in installoptionalpackage.
comment:7 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | in-progress → closed |
Implemented in hrev45414. Thanks!
follow-up: 9 comment:8 by , 12 years ago
There are some possibly abandoned titles like Bracker that it would be great to see if they still worked. Thanks for your help! -K
comment:9 by , 12 years ago
Replying to Kev:
There are some possibly abandoned titles like Bracker that it would be great to see if they still worked. Thanks for your help! -K
Just to be clear: this package isn't a requirement to run R5 apps in general, it only exists to support a handful of apps that aren't well-behaved and make assumptions about the on-disk folder layout.
follow-up: 11 comment:10 by , 12 years ago
So the kind of thing that would fix a 'missing lib' error but not a crash.
comment:11 by , 12 years ago
Replying to Kev:
So the kind of thing that would fix a 'missing lib' error but not a crash.
Mm, no, missing lib would be a different issue. What it'd be most likely to fix is random errors/complaints about not being able to find/read/write various files while the app's running.
Yes. The warning is there to tell app devs that those links won't be available forever, since they're mainly there for badly written apps which hardcoded paths instead of using find_directory().