<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 5/11/2014 5:59 PM, Maciej (Matchek)
Bliziński wrote:<br>
</div>
<blockquote
cite="mid:CALtRa-5M7BjxeBSDa-m_8yQ3mgyEharE=khw0JX53YVGZJSqRQ@mail.gmail.com"
type="cite">
<p dir="ltr">Em 06/05/2014 06:08, "Gordon Marler" <<a
moz-do-not-send="true" href="mailto:gmarler@opencsw.org">gmarler@opencsw.org</a>>
escreveu:<br>
> Stripping out the features in mgar that are native to IPS
is probably important, to avoid duplication of effort.</p>
<p dir="ltr">My idea was to use "mgar merge" to get the pkgroot
directory. Then we could use any means necessary to build an IPS
package front that pkgroot, taking as much information as
possible from the GAR build recipe. Then we would ask Dago for
help in integrating it into GAR. </p>
<p dir="ltr">Gordon, do you think it's possible to start that way?
Is anything blocking you?</p>
</blockquote>
Sounds reasonable. Just getting myself reactivated and up to speed
now. IRC (I'll be gmarler, duh), and reading up on all that's
changed while I've been "dormant".<br>
<br>
I guess the only thing slowing me down would be this:<br>
<br>
- I suppose we'll be starting this IPS repo from scratch, so I'd
better start building packages from the foundation up, and we'll fix
items as they show up as obstacles along the way. Is there a nice
way to either see or generate a dependency list of the package chain
from the bottom up? That'll provide a nice map to follow.<br>
<br>
Separately, and I'll probably see this shortly, but is there a
Solaris 11 x86 or SPARC system in the buildfarm? If not, I have an
x86 variant available. Having a SPARC M-x000 or T4 or higher will
be required if we want to have dual binary builds for each package,
which IPS supports now. If not, it's easily added later.<br>
<br>
<blockquote
cite="mid:CALtRa-5M7BjxeBSDa-m_8yQ3mgyEharE=khw0JX53YVGZJSqRQ@mail.gmail.com"
type="cite">
<p dir="ltr">Maciej</p>
</blockquote>
<br>
</body>
</html>