On Fri, 26 Sep 2008, Nils Breunese (Lemonbit) wrote:
Dag Wieers wrote:
Why is it blowing people off if I say that apt does not have this problem ?
It's not that exactly, it's indirectly saying that you don't care about your
yum users what was blowing me off. As someone else already said: the
distributions that you support all use yum by default, your repository is
pretty popular and you provide a yum repository.
I also support EL2, RH7, RH9, EL3 and EL4. None of these were using yum
until CentOS came into the picture. In fact I have been using them since
RHEL2 with apt and never had the problems that yum users are reporting.
BTW Apt uses the yum metadata.
So a lot of people expect
the repository not to cause any trouble when they add it to their
configuration. When you knowingly leave the repository in a state with broken
dependencies that is a sure way to get people mailing to the list with
complaints, especially when you don't let people know by posting here.
The repository only gives problems if you have audacity installed.
But I totally understand your argument about having limited time, etc.
Ultimately it's your repo, it's your call. :o)
Right. Thanks :-)
I think yum should be more resilient, but I have been saying that for years
and nobody did anything about it. I don't care because I don't use it as
long as I can use apt and yum is still in its infancy.
We can argue whether the above is true, but I have no time to fix yum, I am
not interested in spending more time to maintain more infrastructure.
rpmrepo was going to be the solution, but apparently is either not having
enough manpower or nobody driving it.
I am not interested in driving rpmrepo because I have no more freetime.
And I don't mind that people complain it is not working, I do mind that
they are not helping to solve the issue.
I understand if you choose to not spend any time on making sure your yum
repository is in good shape, but you might maybe want to advertise that fact
on the website then or something, so people can anticipate and know you don't
care about yum. They might just switch to apt. :o) I do see people asking
what could be done to help, but I don't see you replying to them. I also
wouldn't know what I could do other than try and help people on this list. I
guess you need people that know how to package stuff?
There is an rpmrepo website and mailinglist. I don't know what could be
done, I don't know what is blocking the project.
And maybe it is very egoistic of me to update wxGTK when I needed truecrypt
and at the same time broke audacity. But then again we have people complain
that EPEL is not compatible with RPMforge because they have wxGTK 2.8.
I believe you and EPEL never were very compatible, right? Are you now trying
to be compatible with EPEL?
I don't think we ever were incompatible on purpose. But if I have a need
for wxGTK 2.8 for truecrypt and it also makes me more compatible with
EPEL, it gives me more reasons for doing it. Even if in the end audacity
falls off.
So I cannot do good anyway, so I prefer to do myself good :-)
Sure. As I said: it's your call.
And a call to my users...
--
-- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
