Re: Overeager cleaning of -devel provides
Jeff Johnson <[email protected]> Fri, 2 Aug 2013 10:55:11 -0400
| Newsgroups | gmane.linux.mandrake.cooker.devel |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail=_A22F3C19-0612-4D73-AB81-72F947512692 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Aug 2, 2013, at 7:10 AM, Guy Bormann wrote: >>=20 > I guess it helps as a distributor to have main contributors that also > 'own' the upstream or work for the largest Linux company. >=20 Presumably you are snidely remarking on RedHat and the degree of=20 involvement in FL/OSS projects. But "own" is troll bait and "largest" isn't exclusive. > Of course you can make a -devel package arch-agnostic, you just hide = the > complexity in the package (and make it bigger because you need to = store > all supported archs even if you don't need the other part)...for every > single package instead of in the packaging system. The KISS you see is > very superficial. >=20 This isn't the correct characterization of the problem. The issue is arch-specific differing content in include (usually, not = always) files causing file conflicts. Different content on same path can be handled either by merging (like = Fedora has done) or by adding an arch identifier and changing include paths (like = Mandriva has done). The changes are usually quite small (not "bigger") to merge, with a = pleasant result that there are fewer files to examine when a build breaks. The idea that content for "all supported arches" leads to bloat ignores = the fact that most user machines don't need to install -devel packages at all. > That's assuming -devel packages only every contain C/C++ header = files... >=20 Again the multi-arch issue has to do with files, not packages. There is = no assumption that -devel packages contain on header files implied. 73 de Jeff --Apple-Mail=_A22F3C19-0612-4D73-AB81-72F947512692 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii <html><head></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; = "><br><div><div>On Aug 2, 2013, at 7:10 AM, Guy Bormann wrote:</div><br = class=3D"Apple-interchange-newline"><blockquote = type=3D"cite"><div><blockquote type=3D"cite"><br></blockquote>I guess it = helps as a distributor to have main contributors that also<br>'own' the = upstream or work for the largest Linux = company.<br><br></div></blockquote><div><br></div>Presumably you are = snidely remarking on RedHat and the degree = of </div><div>involvement in FL/OSS = projects.</div><div><br></div><div>But "own" is troll bait and "largest" = isn't exclusive.</div><div><br><blockquote type=3D"cite"><div>Of course = you can make a -devel package arch-agnostic, you just hide = the<br>complexity in the package (and make it bigger because you need to = store<br>all supported archs even if you don't need the other = part)...for every<br>single package instead of in the packaging system. = The KISS you see is<br>very = superficial.<br><br></div></blockquote><div><br></div>This isn't the = correct characterization of the problem.</div><div><br></div><div>The = issue is arch-specific differing content in include (usually, not = always) files causing</div><div>file = conflicts.</div><div><br></div><div>Different content on same path can = be handled either by merging (like Fedora has done)</div><div>or by = adding an arch identifier and changing include paths (like Mandriva has = done).</div><div><br></div><div>The changes are usually quite small (not = "bigger") to merge, with a pleasant result</div><div>that there are = fewer files to examine when a build breaks.</div><div><br></div><div>The = idea that content for "all supported arches" leads to bloat ignores the = fact that most</div><div>user machines don't need to install -devel = packages at all.</div><div><br></div><div><blockquote = type=3D"cite"><div>That's assuming -devel packages only every contain = C/C++ header files...<br><font class=3D"Apple-style-span" = color=3D"#0a7618"><br></font></div></blockquote><br></div><div>Again the = multi-arch issue has to do with files, not packages. There is no = assumption</div><div>that -devel packages contain on header files = implied.</div><div><br></div><div>73 de Jeff</div><br></body></html>= --Apple-Mail=_A22F3C19-0612-4D73-AB81-72F947512692--