<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi,<br>
</p>
<div class="moz-cite-prefix">Le 31/10/2018 à 20:05, Dumont, Joey a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:dfb972670b304de285ea37f7e2b1680a@DC01ZWH0015.Corp.nrc.gc.ca">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#212121">Hi everyone!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#212121">Our group is
thinking of maintaining a subset of the msys2 repo to be
used internally. I am wondering if there is documentation on
the Arch Linux side on what tools you are currently using to
automatically build the packages in the officially supported
repos.</span></p>
</div>
</blockquote>
<p>Almost none, we mostly build by hand. We have
<a class="moz-txt-link-freetext" href="http://rebuilds.foutrelis.com/">http://rebuilds.foutrelis.com/</a> for huge rebuilds though.
Automation of rebuilds is somewhere on the agenda (but we would
prefer to have reproducible builds first I guess).<br>
</p>
<blockquote type="cite"
cite="mid:dfb972670b304de285ea37f7e2b1680a@DC01ZWH0015.Corp.nrc.gc.ca">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#212121"> I believe
there must be some kind of dependency management as well,
since official repos are never cursed by soname bump issues.</span></p>
</div>
</blockquote>
<p>When a package has a soname dump (something we can detect with
checkpkg for instance), we generate a todo list
(<a class="moz-txt-link-freetext" href="https://www.archlinux.org/todo/">https://www.archlinux.org/todo/</a>) of depending packages to rebuild
(using a script called sogrep).<br>
</p>
<blockquote type="cite"
cite="mid:dfb972670b304de285ea37f7e2b1680a@DC01ZWH0015.Corp.nrc.gc.ca">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#212121"> Is there
documentation on this as well? Specifically, is there a tool
similar to apt-mirror?</span></p>
</div>
</blockquote>
<p>I don’t know the specifics about mirrors/repos, but I think it’s
pretty easy to setup.</p>
<p>Regards,<br>
Bruno<br>
</p>
</body>
</html>