Hello to you!
First of all i want you to know the following facts:
1. there are people dedicated to games packaging but those people
maintain a really huge number of packages.
2. there are lots of very interesting games, even 3d games that are
not part of extras yet
So this is why I write this email. We need more people dedicated to
package games. Especially initial packaging of games takes alot work
usually for various reasons.
If anyone is interested to maintain some of the next generation games
in extras you can either:
a) look at the games sig on the fedora wiki
b) contact me as i have various things initially packaged but not
ready for extras inclusion also a lack of time to really maintain the
packages in extras because i am too often on the road... but still
sometimes spare time to invest into building initial packages
b) look around for a yet unknown/unpackaged open source game
What i have ready e.g. would be warzone2100, vdrift (vdrift.net) and a
few others, so if youd like to take those i can send you a halfway
finished spec file.
Some of us were talking previously about how to make it easier to keep
down the general problem of dependency bloat - e.g. to spot when the
"core" group is pulling in packages which it shouldn't. What kind of a
tool would help?
The workflow we thought would be best was:
1) Pull out the list of packages and their dependencies which you're
interested (e.g. the "core" group, the kernel and its deps, the
"desktop" group etc.)
2) Browse through the list of packages and identify anything that
3) For any package which looks strange, look through which packages
pull it in and see if it makes sense
So, I've hacked up a first-cut at a tool like this:
To build do e.g.:
$> wget http://people.redhat.com/markmc/depsgraph/depsgraph-0.30.tar.bz2
$> rpmbuild -ta depsgraph-0.30.tar.bz2
$> rpm -Uhv /usr/src/redhat/RPMS/i386/depsgraph-0.30-1.i386.rpm
To use, first set up a repo with what you want to look at:
$> mkdir test-repo && cd test-repo
$> repotrack -r core kernel && createrepo -p .
Then look out for anything that you wouldn't expect in the repo and do:
$> depsgraph file:///home/markmc/trash/trepo1 python
See the attached screenshot showing this bug:
Can anyone tell me what the status of wpa_supplicant development is?
I tried to change over from WEP to WPA in fc6 and hit a brick wall.
>From postings all over the net it seems that the vast majority of
people who try to get wpa going come across problems and struggle to
get anything working properly. The support for different hardware
seems erratic and largely undocumented.
It appears to me that there is a need for some development as well as
some decent documentation to help people with this issue.
What do others think?
I'm sure we have all heard about yum's "speed" issues, and yes it is
annyoing, but fc6 went a long way to try to improve this speed. FC6 also saw
yum become even more integrated into fedora (anaconda etc.). And all this
development is good, and don't get me wrong I think yum is a fantastic tool
with many wonderful features. However it's currently still lacking in some
1. The GUI
pup and pirut are pretty good programs but they are in some ways, a bit
restricting. (for lack of a better word). I think that they should have more
then just a progress bar. They should also output more information about
say, the size of the files. How much (exactly) has been downloaded, and
perhaps at what speed the downloads are going.
2. yum CLI
Yum's CLI is much better than the gui tools at this point, and though it has
gotten better there are some ways that it still needs to improve. The two
areas I find most...upsetting involved the headers and dependency
resolution. The headers are quite large....ok so maybe the biggest they get
is around 400k (if I recall correctly) but when your on a slower connection,
and your upgrading a lot of packages this can be quite annoying. Perhaps
they header files could be placed in a different, smaller, format. Or an
option to download all the header files could be included, and the headers
can be updated then along with the metadata. The other, and in my opinion
more important, area the yum cli should improve is in the resolution of
dependencies, it should be faster. Currently yum seems just as good as
apt-get or smart-pm or packman (arch linux's tool) at resolving dependecies.
Yet all the other package manager do it much faster, almost instantly. I'm
not sure why that is. It seems that it does each package one by one slowly.
I think this may relate to the way the headers are stored. What makes these
improvements to the cli so important is that if they are done they will
benifit puplet and pirut, as well as anaconda's installation tool. And thus
I view the ClI improvments to be very important.
Please don't misunderstand, I'm not complaining. I'm stating areas that I
(based solely on what I have gathered from my usage of fedora an yum) feel
that yum can improve. A friend of mine along with myself plan to start
looking at the yum code to try to see what we can do to improve yum, with
our basic programming skills. However I decided it would be best to work
directly with the devs on this one. My goal is to start a discussion on the
issue to see what the fedora devs, especially those involved directly with
yum, had to say about this. And perhaps we can help in this area.
Thank you for your time.
p.s. This was the best place I could find to post this, if there is a better
place to do this (a yum-devel list) please notify me and I will take this
I'm not sure who to contact this about this issue : The Fedora Planet RSS
feed seem to be broken : http://fedoraproject.org/people/rss20.xml
It seems to be broken by a link in David Lutterkort's entry
about "Kickstarting into puppet".
Who should I contact to report this bug ?
http://aurelien.bompard.org ~~~~ Jabber : abompard(a)jabber.fr
"Backups are for wimps. Real men upload their work to an ftp server
and have everybody mirror it." -- Linus Torvalds