Re: llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-09 Thread James Antill
On Wed, 2010-06-09 at 08:38 +0530, Rahul Sundaram wrote: On 06/09/2010 05:00 AM, Kevin Kofler wrote: Michel Alexandre Salim wrote: Any idea how to fix this? We should probably add a section to the packaging guidelines, on how to migrate to noarch subpackages without breaking upgrade

llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-08 Thread Michel Alexandre Salim
An LLVM user reported to me a problem updating LLVM (from the version in F13-updates to the version that is then in Koji), and I suggested that he filed a bug report. https://bugzilla.redhat.com/show_bug.cgi?id=600969 In the discussion that follows, James Antill diagnosed the problem as due to

Re: llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-08 Thread Kevin Kofler
Michel Alexandre Salim wrote: Any idea how to fix this? We should probably add a section to the packaging guidelines, on how to migrate to noarch subpackages without breaking upgrade paths. Or just not support users who have unneeded multilib packages installed. Installing only those multilib

Re: llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-08 Thread Rahul Sundaram
On 06/09/2010 05:00 AM, Kevin Kofler wrote: Michel Alexandre Salim wrote: Any idea how to fix this? We should probably add a section to the packaging guidelines, on how to migrate to noarch subpackages without breaking upgrade paths. Or just not support users who have unneeded

Re: llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-08 Thread Kevin Kofler
On Wednesday 09 June 2010, Rahul Sundaram wrote: As long as yum offers it as a option, bugs must be fixed. Nonsense. There are plenty of options in software we ship which we don't and can't support. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org

Re: llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-08 Thread Rahul Sundaram
On 06/09/2010 09:58 AM, Kevin Kofler wrote: On Wednesday 09 June 2010, Rahul Sundaram wrote: As long as yum offers it as a option, bugs must be fixed. Nonsense. There are plenty of options in software we ship which we don't and can't support. Then stop including such a option

Re: llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-08 Thread Kevin Kofler
On Wednesday 09 June 2010, Rahul Sundaram wrote: On 06/09/2010 09:58 AM, Kevin Kofler wrote: Nonsense. There are plenty of options in software we ship which we don't and can't support. Then stop including such a option or mark it unsupported or experimental. A lot of software we ship

Re: llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-08 Thread Rahul Sundaram
On 06/09/2010 10:13 AM, Kevin Kofler wrote: A lot of software we ship supports more than just Fedora, you just can't expect all options to work on Fedora. As for yum in particular, there are plenty of ways to end up with a broken setup by modifying yum.conf, e.g. exclude=kdelibs will

Re: llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-08 Thread Seth Vidal
On Wed, 9 Jun 2010, Rahul Sundaram wrote: I don't buy your argument and trashing anyone's opinion you disagree with you as crap and nonsense is hardly going to help make your case. Excluding a dependency and setting a multi_lib option is hardly the same thing. Anyway, I am pretty sure

Re: llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-08 Thread Rahul Sundaram
On 06/09/2010 10:23 AM, Seth Vidal wrote: a suggestion. Since neither of you speak for any of the yum developers, please stop doing so either implicitly or explicitly. I am not speaking for you any yum developers implicitly or explicitly. I am expressing a view point. You can as a yum

Re: llvm case study: yum's handling of newly-converted noarch subpackages

2010-06-08 Thread Kevin Kofler
On Wednesday 09 June 2010, Seth Vidal wrote: Since neither of you speak for any of the yum developers, please stop doing so either implicitly or explicitly. I'm not speaking for any of the yum developers. I'm just suggesting we, Fedora, stop caring about bizarre yum options which we don't