Josh Boyer wrote:
On Tue, 2007-05-15 at 23:25 +0530, Rahul Sundaram wrote:
Josh Boyer wrote:
On Tue, 2007-05-15 at 23:12 +0530, Rahul Sundaram wrote:
As such I think Rahul is shooting way over the top with
pulling them from the repo, as that creates even more trouble for users.
Package is broken. Maintainer refuses to fix it. Others are not
interested. Pulling the packages is the right way to go since they are
implicitly orphaned packages. What alternative are you suggesting?
That's not quite true in this case. The package isn't broken. The tag
on which it sits is. Just clarifying that.
Purely from the end user perspective what difference does it make? I
None. But then again, neither does your suggestion of pulling the
packages out of the repo :).
It does make a pretty big difference in the overall quality of the
repository. I can solidly claim that every single package in the release
has a good update path. Quality and robustness of the repository and
updates is one of the biggest problems we need to tackle. I see people
suggesting that pulling off packages is over the top but I dont see
anyone suggesting any other alternative. Does anyone want to knowingly
put packages into the release with fundamental issues like this?
There is a usability issue in that packages being dropped are not
immediately visible to end users. There are other potential solutions or
that. I have already suggested before to have a live upgrade
tool/Anaconda module which checks for packages that does not have a
proper update path (Packages that orphaned/pulled off the repository for
any other reasons such as licensing, improperly configured third party
repository packages ,custom packages etc) and list them with any
possible solutions.
Rahul
--
Fedora-maintainers mailing list
Fedora-maintainers@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers
--
Fedora-maintainers-readonly mailing list
Fedora-maintainers-readonly@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
