Opened 12 years ago

Closed 6 years ago

#2609 closed bug (invalid)

/boot/beos/apps/* should have symlinks inside /boot/apps

Reported by: bga Owned by: stippi
Priority: low Milestone: R1
Component: File Systems Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Platform: All


In BeOS, all aplications inside /boot/beos/apps were symlinked inside /boot/apps. The reason was because /boot/apps was supposed to be a place where the user finds all applications available.

Other than that, some R5 programs (like SpicyKeys) launch programs like the Terminal by path and tries to launch it as /boot/apps/Terminal, which obviously fails.

I guess this is part of the R5 compatibility goal.

Change History (4)

comment:1 by axeld, 12 years ago

I don't know, using this path inside of applications isn't a good idea, as /boot/apps/ is user territory - ie. they can and will change it to their needs.

Besides that, I don't see much point in providing those links, at least not just for compatibility. Isn't SpicyKeys completely configurable, anyway?

What do others think about this?

comment:2 by bga, 12 years ago

I am not arguing it is a good idea, I am just pointing out that Be decided bootapps would hold all applications. The ones shipped with BeOS wpuld be symlinked there and the user could also install other applications. This looks like a nice approach to me as the user just need to go to one single place to find his applications (unless he/she intentionally deletes links from there or install things in other places, of course).

SpicyKeys was just an example as it comes pre-configured with those paths. There could be other applications that rely on this behaviour.

comment:3 by humdinger, 7 years ago

Now with package management this is pretty much unavoidable. Close as invalid?

comment:4 by waddlesplash, 6 years ago

Component: User InterfaceFile Systems
Resolution: invalid
Status: newclosed

Yes, PM does indeed invalidate this.

Note: See TracTickets for help on using tickets.