Heads up; F22 will require applications to ship appdata to be listed in software center
hlhowell at pacbell.net
Sun Jan 26 16:27:18 UTC 2014
On Sun, 2014-01-26 at 12:14 +0100, Lars E. Pettersson wrote:
> On 01/26/2014 11:08 AM, drago01 wrote:
> > gcc isn't an application in a sense of "gui application" so there is
> > to ways to install it
> > either the user installs an IDE which pulls it in as dep or he/she
> > installs it using yum/dnf.
> Would it not be better to have a 'software center' that includes ALL
> software available, be they GUI related or not? Probably based on
> rpm-packages, as that is what our system ultimately relies on. A GUI to
> handle ALL software available would be better, than one only installing
> GUI-related software, in my opinion.
> >> How does 'application' correlates to a rpm-package?
> > Application means GUI application that has a .desktop file.
> That makes the 'software center' of lesser use, as the user will be
> confused when he/she does not find the program/rpm-package/application
> he/she wants to install.
> Lars E. Pettersson <lars at homer.se>
Another issue, I think, deals with useful command line tools, such as
python scripts, grep, or such utilities as are yet to be developed. Not
all things are gui based, and not being gui based doesn't mean that
users won't want or use them.
Even most gui programs that do exist had lots of code developed before
being transferred to a gui. Working from a command line, with a
compiler and debugger is also a good introduction to the actual
functioning of a computer and gets one closer to the "bare iron", which
permits the leveraging of basic knowledge. Of course, this is just my
personal opinion. When I work on developing new stuff, the gui is often
put off until I get basic code working. The gui essentially clothes the
code to simplify the command interface, cut down on typos, and provide
prompts for arguments etc. all to assist the user manage and benefit
from whatever code is run.
More information about the devel