Follow-up Comment #2, bug #24677 (project gnustep):
> I disagree, it should install into SYSTEM, as all SYSTEM applications.
What is a "SYSTEM application" though ?
For me, it is something that comes with my system, as opposed to something
that I install manually myself (which is a "LOCAL application").
And the difference is useful because my system is usually installed from a CD
or using RPMs or DEBs or an installer ... and "system applications" are part
of that and I don't want to mess with them.
If I install manually stuff myself from source, I want it to go in a separate
directory. That way I know what I installed myself from source and what comes
from the
system, and they are separate. Eg, I can upgrade my system without
destroying my
manually installed stuff, and installing manually stuff won't prevent me from
upgrading. If things go really wrong, I can easily uninstall everything I
installed
manually - because it's in a separate directory.
This is all to say that what is a "SYSTEM application" and what is a "LOCAL
application" depends on how they are installed. SystemPreferences - or Gorm
-
can be a "SYSTEM application" or a "LOCAL application" depending on where
you get it from. If it's part of your system installation (eg, an RPM) it's
a
"SYSTEM application". If you install it yourself from source it's a "LOCAL
application".
Now when you install SystemPreferences from sources, by definition it's
a LOCAL application and it should go in LOCAL. ;-)
A packager will need to install it in SYSTEM when creating the package.
I hope that clarifies the logic.
Thanks
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?24677>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
