Help wanted removing --vendor from spec files
by Toshio Kuratomi
Greetings Games SIG, this is a request for help in cleaning up one area of
spec files that has affected a good many games packages.
== Background ==
For Fedora 19 we're trying to get rid of the vendorization of .desktop
files. This is a legacy of Fedora Extras and early Fedora days when
Guidelines specified that .desktop files should be installed with:
desktop-file-install --vendor "fedora" [...]
It was realized after a few releases that desktop-file-install's
--vendor flag caused issues because its implementation was to rename the
.desktop file; prepending the value of vendor to the filename. In the past
we decided that new packages would not use --vendor but that packages that
already did so must keep doing so. This is because software that customized
the menus would likely copy the .desktop file (complete with the vendor
prefix). If we stopped installing with --vendor, anyone who customized
those entries in their menus would end up with two entries because none of
the software would be able to figure out that the entries were really for
the same thing.
For Fedora 19 we (FPC and FESCo) have decided that it's time to get rid of
this legacy behaviour. If we can get rid of --vendor in all spec files for
F19 and above, then users will only suffer ill effects once, when they
upgrade from a previous release to F19. Getting rid of vendor will solve
issues for GNOME3 and other softweare which doesn't handle the file renaming
that --vendor does so now is a good time to do so.
== Help Needed ==
I've assembled a list of packages that are installing .desktop files with
as well as some tips for porting spec files so that they can work on both
Fedora 19+ and older Fedora and EPEL releases. a few provenpackagers have
been working on the list of packages but it is a slow process with so many
packages to change. It would be great if more people would join in. There
are a lot of games in the list of packages so I was hoping that some people
from the games SIG might either modify their own packages and check them off
the list or, if they're provenpackagers, join in in porting any packages
that are using --vendor to no longer use it in F19+.
It would be great if we could get this done before Fedora 19 branches from
rawhide (2013-03-12) as after that date we'll have to modify packages in two
branches, the F19 and Rawhide trees.
Thanks for any help,
10 years, 1 month
Re: testing fedora redeclipse 1.3.1 packaging
by Martin Erik Werner
Hi testers and gamesers!
The latest version (1.3.1) of Red Eclipse has been brewing in testing
for quite a while now (and upstream is already planning for a soonish
1.4), and I was wondering if there would be anyone interesting in poking
it a bit and see if it can get pushed into updates.
I'm copy-pasting an older post with testing hints below, these should
still apply to this new version.
On Sun, 2012-06-03 at 16:21 +0200, Martin Erik Werner wrote:
> There are some basic testing hints at:
> I'm not sure what the process is with a new package, and if using a
> clean system is a necessity... I'm not at all very familiar with the
> Fedora process, as it were.
> If I would do a rough checklist myself:
> 1. Test installing and uninstalling of all packages:
> $ yum install redeclipse redeclipse-server redeclipse-data cube2font
> $ yum remove redeclipse redeclipse-server redeclipse-data cube2font
> 2. Check if the game client runs, can play offline, and play on the main
> online server:
> $ redeclipse
> $ redeclipse -x"dm bath"
> $ redeclipse -x"connect play.redeclipse.net"
> 3. Test if the game server runs and is accessible via the master
> - Mind that a server connected to the master (for a longer time)
> should follow some guidelines, and will be community-moderated, c.f.
> - Default ports for RE are 28801-28802
> $ redeclipse-server -x"sv_serverdesc $USER testserver"
> $ redeclipse -x"showgui servers"
> - Try to connect to your own server via the master server list
> 4. Check that server config examples docs, and manpages exist:
> $ ls /usr/share/doc/redeclipse/examples/
> $ man redeclipse
> $ man redeclipse-server
> $ man cube2font
> 5. Check that cube2font can make a font:
> $ cube2font /usr/share/fonts/dejavu/DejaVuSans.ttf default 3 19 1 1
> 49 49 512 512 32 64 packages/fonts
> 6. Check that redeclipse has a correctly scaled icon, and a desktop
> entry, as would be expected in your desktop manager.
> 7... Anything else you can think of that I missed ;)
Martin Erik Werner <martinerikwerner(a)gmail.com>
10 years, 3 months