PSA: If you’re using
appdata-validate, please switch to
appstream-util validate from the appstream-glib project. If you’re also using the M4 macro, just replace
APPSTREAM_XML. I’ll ship both the old binary and the old m4 file in appstream-glib for a little bit, but I’ll probably remove them again the next time we bump ABI. That is all.
By hughsie on October 30, 2014
PSA: If you’re using
By hughsie on October 15, 2014
A few people have asked me now “How do I make my font show up in GNOME Software” and until today my answer has been something along the lines of “mrrr, it’s complicated“.
What we used to do is treat each font file in a package as an application, and then try to merge them together using some metrics found in the font and 444 semi-automatically generated AppData files from a manually updated .csv file. This wasn’t ideal as fonts were being renamed, added and removed, which quickly made the .csv file obsolete. The summary and descriptions were not translated and hard to modify. We used the pre-0.6 format AppData files as the MetaInfo specification had not existed when this stuff was hacked up just in time for Fedora 20.
I’ve spent the better part of today making this a lot more sane, but in the process I’m going to need a bit of help from packagers in Fedora, and maybe even helpful upstreams. This are the notes of what I’ve got so far:
Font components are supersets of font faces, so we’d include fonts together that make a cohesive set, for instance,”SourceCode” would consist of “SoureCodePro“, “SourceSansPro-Regular” and “SourceSansPro-ExtraLight“. This is so the user can press one button and get a set of fonts, rather than having to install something new when they’re in the application designing something. Font components need a one line summary for GNOME Software and optionally a long description. The icon and screenshots are automatically generated.
So, what do you need to do if you maintain a package with a single font, or where all the fonts are shipped in the same (sub)package? Simply ship a file like this in
/usr/share/appdata/Liberation.metainfo.xml like this:
<?xml version="1.0" encoding="UTF-8"?> <!-- Copyright 2014 Your Name <you@domain> --> <component type="font"> <id>Liberation</id> <metadata_license>CC0-1.0</metadata_license> <name>Liberation</name> <summary>Open source versions of several commercial fonts</summary> <description> <p> The Liberation Fonts are intended to be replacements for Times New Roman, Arial, and Courier New. </p> </description> <updatecontact>richard_at_hughsie_dot_com</updatecontact> <url type="homepage">http://fedorahosted.org/liberation-fonts/</url> </component>
There can be up to 3 paragraphs of description, and the summary has to be just one line. Try to avoid too much technical content here, this is designed to be shown to end-users who probably don’t know what TTF means or what MSCoreFonts are.
It’s a little more tricky when there are multiple source tarballs for a font component, or when the font is split up into subpackages by a packager. In this case, each subpackage needs to ship something like this into
<?xml version="1.0" encoding="UTF-8"?> <!-- Copyright 2014 Your Name <you@domain> --> <component type="font"> <id>LiberationSerif</id> <metadata_license>CC0-1.0</metadata_license> <extends>Liberation</extends> </component>
This won’t end up in the final metadata (or be visible) in the software center, but it will tell the metadata extractor that
LiberationSerif should be merged into the
Liberation component. All the automatically generated screenshots will be moved to the right place too.
Moving the metadata to font packages makes the process much more transparent, letting packagers write their own descriptions and actually influence how things show up in the software center. I’m happy to push some of my existing content from the .csv file upstream.
These MetaInfo files are not supposed to replace the existing fontconfig files, nor do I think they should be merged into one file or format. If your package just contains one font used internally, or where there is only partial coverage of the alphabet, I don’t think we want to show this in GNOME Software, and thus it doesn’t need any new MetaInfo files.
By hughsie on September 29, 2014
In GNOME 3.14 we show any valid application in the software center with an application icon of 32×32 or larger. Currently a 32×32 icon has to be padded with 16 pixels of whitespace on all 4 edges, and also has to be scaled x2 to match other UI elements on HiDPI screens. This looks very fuzzy and out of place and lowers the quality of an otherwise beautiful installing experience.
For GNOME 3.16 (Fedora 22) we are planning to increase the minimum icon size to 48×48, with recommended installed sizes of 16×16, 24×24, 32×32, 48×48 and 256×256 (or SVG in some cases). Modern desktop applications typically ship multiple sizes of icons in known locations, and it’s very much the minority of applications that only ship one small icon.
Soon I’m going to start nagging upstream maintainers to install larger icons than 32×32. If you’re re-doing the icon, please generate a 256×256 or 64×64 icon with alpha channel, as the latter will probably be the minimum size for F23 and beyond.
At the end of November I’ll change the minimum icon size in the AppStream generator used for Fedora so that applications not fixed will be dropped from the metadata. You can of course install the applications manually on the command line, but they won’t be visible in the software center until they are installed.
If you’re unclear on what needs to be done in order to be listed in the AppStream metadata, refer to the guidelines or send me email.
By hughsie on September 25, 2014
Last time I blogged about AppStream I announced that over 25% of applications in Fedora 21 were shipping the AppData files we needed. I’m pleased to say in the last two months we’ve gone up to 45% of applications in Fedora 22. This is thanks to a lot of work from Ryan and his friends, writing descriptions, taking screenshots and then including them in the fedora-appstream staging repo.
So fedora-appstream doesn’t sound very upstream or awesome. This week I’ve sent another 39 emails, and opened another 42 bugs (requiring 17 new bugilla/trac/random-forum accounts to be opened). Every single file in the fedora-appstream staging repo has been sent upstream in one form or another, and I’ve been adding an XML comment to each one for a rough audit log of what happened where.
Some have already been accepted upstream and we’re waiting for a new tarball release; when that happens we’ll delete the file from fedora-appstream. Some upstreams are really dead, and have no upstream maintainer, so they’ll probably languish in fedora-appstream until for some reason the package FTBFS and gets removed from the distribution. If the package gets removed, the AppData file will also be deleted from fedora-appstream.
Also, in the process I’ve found lots of applications which are shipping AppData files upstream, but for one reason or another are not being installed in the binary rpm file. If you had to tell me I was talking nonsense in an email this week, I apologize. For my sins I’ve updated over a dozen packages to the latest versions so the AppData file is included, and fixed a quite a few more.
Fedora 22 is on track to be the first release that mandates AppData files for applications. If upstream doesn’t ship one, we can either add it in the Fedora package, or in fedora-appstream.
By hughsie on August 29, 2014
While working on the preview of GNOME Software for Fedora 20, one problem became very apparent: When you launched the “Software” application for the first time, it went and downloaded metadata and then built the libsolv cache. This could take a few minutes of looking at a spinner, and was a really bad first experience. We tried really hard to mitagate this, in that when we ask PackageKit for data we say we don’t mind the cache being old, but on a LiveCD or on first install there wasn’t any metadata at all.
So, what are we doing for F21? We can’t run packagekitd when constructing the live image as it’s a D-Bus daemon and will be looking at the system root, not the live-cd root. Enter
packagekit-direct. This is an admin-only tool (no man page) installed in
/usr/libexec that designed to be run when you want to run the PackageKit backend without getting D-Bus involved.
For Fedora 21 we’ll be running something like
DESTDIR=$INSTALL_ROOT /usr/libexec/packagekit-direct refresh in
fedora-live-workstation.ks. This means that when the Live image is booted we’ve got both the distro metadata to use, and the libsolv files already built. Launching gnome-software then takes 440ms until it’s usable.
By hughsie on July 8, 2014
Today we reached an important milestone. Over 25% of applications in Fedora now ship AppData files. The actual numbers look like this:
- Applications with descriptions: 262/1037 (25.3%)
- Applications with keywords: 112/1037 (10.8%)
- Applications with screenshots: 235/1037 (22.7%)
- Applications in GNOME with AppData: 91/134 (67.9%)
- Applications in KDE with AppData: 5/67 (7.5%)
- Applications in XFCE with AppData: 2/20 (10.0%)
- Application addons with MetaInfo: 30
We’ve gone up a couple of percentage points in the last few weeks, mostely from the help of Ryan Lerch, who’s actually been writing AppData files and taking screenshots for upstream projects. He’s been concentrating on the developer tools for the last week or so, as this is one of the key groups of people we’re targetting for Fedora 21.
One of the things that AppData files allow us to do is be smarter suggesting “Picks” on the overview page. For 3.10 and 3.12 we had a farly short static list that we chose from at random. For 3.14 we’ve got a new algorithm that tries to find similar software to the apps you already have installed, and also suggests those. So if I have Anjunta and Devhelp installed, it might suggest D-Feet or Glade.
By hughsie on July 2, 2014
Are you a pixel perfect kind of maintainer? Frustrated by slight blurriness in screenshots when using GNOME Software?
If you have one screenshot, capture a PNG of size 752×423. If you have more than one screenshot use a size of 624×351.
If you use any other 16:9 aspect ratio resolution, we’ll scale your screenshot when we display it. If you use some crazy non-16:9 aspect ratio, we’ll add padding and possibly scale it as well, which is going to look pretty bad. That said, any screenshot is better than no screenshot, so please don’t start removing
By hughsie on June 17, 2014
A lot has been said on fedora-devel in the last few weeks about DNF and Yum. I thought it might be useful to contribute my own views, considering I’ve spent the last half-decade consuming the internal Yum API and the last couple of years helping to design the replacement with about half a dozen of the packaging team here at Red Hat. I’m also a person who unsuccessfully tried to replace Yum completely with Zif in fedora a few years ago, so I know quite a bit about packaging systems and metadata parsing.
From my point of view, the hawkey depsolving library that DNF is designed upon is well designed, optimised and itself built on a successful low-level SAT library that SUSE has been using for years on production level workloads. The downloading and metadata parsing component used by DNF, librepo, is also well designed and complements the hawkey API nicely.
Rather than use the DNF framework directly, PackageKit uses librepo and hawkey to share 80% of the mechanism between PK and DNF. From what I’ve seen of the DNF codebase it’s nice, with unit tests and lots of the older compatibility cruft removed and the only reason it’s not used in PK was that the daemon is written in C and didn’t want to marshal everything via python for latency reasons.
So, from my point of view, DNF is a new command line tool built on 3 new libraries. It’s history may be of a fork from yum, but it resembles more of a 2014 rebuilt American hot-rod with all new motor-sport parts apart from the 1965 modified and strengthened chassis. Renaming DNF to Yum2 would be entirely the wrong message; it’s a new project with a new team and new goals.
By hughsie on June 16, 2014
Public Service Announcement: Debian helpfully defines
datadir to be
/usr/share/games for some packages, which means that the AppData and MetaInfo files get installed into
/usr/share/games/appdata which isn’t picked up by the metadata parsers.
It’s probably safer to install the AppData files into
$datarootdir/appdata as this will work even if a distro has redefined
datadir to be something slightly odd. I’ve changed the examples on the AppData page, but if you maintain a game on Debian with AppData then this might affect you when Debian starts extracting AppSpream metadata in the next few weeks. Anyone affected will be getting email in the next few days, although it only looks to affect very few people.
By hughsie on June 11, 2014
Ever since we rolled out the GNOME Software Center, people have wanted to extend it to do other things. One thing that was very important to the Eclipse developers was a way of adding addons to the main application, which seems a sensible request. We wanted to make this generic enough so that it could be used in gedit and similar modular GNOME and KDE applications. We’ve deliberately not targeted Chrome or Firefox, as these applications will do a much better job compared to the package-centric operation of GNOME Software.
So. Do you maintain a plugin or extension that should be shown as an addon to an existing desktop application in the software center? If the answer is “no” you can probably stop reading, but otherwise, please create a file something like this:
<?xml version="1.0" encoding="UTF-8"?> <!-- Copyright 2014 Your Name Here <firstname.lastname@example.org> --> <component type="addon"> <id>gedit-code-assistance</id> <extends>gedit.desktop</extends> <name>Code Assistance</name> <summary>Code assistance for C, C++ and Objective-C</summary> <url type="homepage">http://projects.gnome.org/gedit</url> <metadata_license>CC0-1.0</metadata_license> <project_license>GPL-3.0+</project_license> <updatecontact>richard_at_hughsie.com</updatecontact> </component>
This wants to be installed into
/usr/share/appdata/gedit-code-assistance.metainfo.xml — this isn’t just another file format, this is the main component schema used internally by AppStream. Some notes when creating the file:
- You can use anything as the
<id>but it needs to be unique and sensible and also match the
- You can use
appstream-util validate gedit-code-assistance.metainfo.xmlif you install appstream-glib from git.
- Don’t put the application name you’re extending in the
<summary>tags — so you’d use “Code Assistance” rather than “GEdit Code Assistance“
- You can omit the
<url>if it’s the same as the upstream project
- You don’t need to create the
metainfo.xmlif the plugin is typically shipped in the same package as the application you’re extending
- Please use
<_summary>if you’re using intltool to translate either your desktop file or the existing appdata file and remember to add the file to POTFILES.in if you use one
Please grab me on IRC if you have any questions or concerns, or leave a comment here. Kalev is currently working on the GNOME Software UI side, and I only finished the metadata extractor for Fedora today, so don’t expect the feature to be visible until GNOME 3.14 and Fedora 21.