#5721: Need application icons and application descriptions
------------------------------+-----------------------
Reporter: rhughes | Owner: rel-eng@…
Type: task | Status: new
Milestone: Fedora 21 Alpha | Component: other
Resolution: | Keywords:
Blocked By: | Blocking:
------------------------------+-----------------------
Comment (by ausil):
Replying to [comment:11 rhughes]:
Replying to [comment:10 ausil]:
> I'm currently on Australian Eastern Standard Time, 4PM GMT is 2AM for
me.
Sorry can't do.
Okay, that's fair enough :) What about 2130 GMT?
2130 GMT is 730 am I can make that.
> Some issues, what you proposed as tooling is a really tiny piece of
the
picture.
Sure, but a tiny part that allows the appdata to stay up to date.
> if you want the data on the mirrors along with the rest of the
metadata the
generation needs to be integrated into createrepo.
The only change I see needed to createrepo would be to cat all the
-icon.tar files
together and also to xmlmerge the new .xml files then gzip
two extra files.
We would need to extract the files from all the rpms and put them together
> you would need some way to get access to the icons and images as
I
really don't want to add that much extra data into the mirrors.
The -icons.tar and .xml file would be just two extra files from the koji
job, just
like the rpms, or the log files.
what koji job? if we wrote a koji plugin to extract them at rpm build time
we would then need to have mash fetch them all together. realistically
though it should be extracted at createrepo time because that then enables
you to make a repo from anywhere and have the data in it.
> which puts us back to a webapp for it, which then opens up a
webstore,
and being able to add a app to all your systems etc.
A webstore is not in scope, and we don't support this multi-system
model. If
you want to do that kind of thing you should be using satellite
or RHN. There are a whole host of sticky problems with doing a web store
like having to upload your package lists to a remote server and having to
depsolve on the remote host which made this model impossible. The privacy,
security and hosting requirements are prohibitive and not what we're going
to do.
not at all. you only need to know which apps are chosen, but anyway its
not on the table right now even if i think its how it should be done.
> I really think it needs to be on the roadmap.
There is not going to be a webapp from the GNOME team, we've designed
and
built a local fat-client for a local system. Either we work together
and host this on the Fedora infrastructure, or we'll have to do something
different that doesn't involve Fedora.
That is your choice, i am trying to work with you here. how big is the
data that we are looking at?
Dennis
--
Ticket URL: <
https://fedorahosted.org/rel-eng/ticket/5721#comment:12>
Fedora Release Engineering <
http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project