Re: Install Cd's?

--===============0882158632317921254==
Content-Type: multipart/signed;
  boundary="nextPart10900366.PSgTyyrJln";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart10900366.PSgTyyrJln
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Monday 28 April 2008, Dean Anderson wrote:
> On Tue, 15 Apr 2008, Tom "spot" Callaway wrote:
> > On Mon, 2008-04-14 at 12:24 -0400, Dean Anderson wrote:
<snip>
> > Pungi works out of the box on sparc, I wrote patches to enable support
> > for sparc, sent them upstream, and they were applied.
> >
> > This is the pungi.conf I'm using:
>
> This pungi.conf is good. Can you put this on the website?
>
> [details omitted in reply]
>
> > Now, to answer your other items:
> >
> > 1. Aurora 1.0 was a port of Red Hat Linux 7.3. Thus, the ancient
> > instructions you found would have worked with it.
>
> Yes. They were just an example. The point was there aren't any similar
> instructions for your current builds.
=46ollow the instructions posted by fedora release engineering if you want =
to=20
create your own spin

> > 2. I did not make any deviations on how SPARC bootable ISOs are created.
> > Upstream mkisofs MADE THE CHANGE. Not me. I told you how I fixed the
> > problem, by passing the proper flags, as documented in both mkisofs and
> > silo (hint, it uses isofs.b). I patched pungi to do the right thing, as
> > it is the Fedora compose tool, sent the patches upstream, upstream took
> > them (this was months, maybe even a year ago).
>
> My point is that these patches should have been on the aurora website a
> year ago; when you made them and long before the upstreams took them,
> because for a while those changes were specific to aurora and
> unpublished.

They were pushed upstream the day that they were created.

> ANY LITTLE CHANGE YOU MAKE, NO MATTER HOW TRIVIAL, NEEDS TO BE
> DOCUMENTED AND PUBLISHED.  And the change needs to be tested in clean
> environment.  Things that work to build an operating system in a porting
> environment don't always work in the built environment.
>
> > 3. If you still have contentions, please, please, do a tiny amount of
> > research before accusing me of things. I'm trying really hard to be
> > patient with you, because I honestly have nothing to hide here, and I do
> > want to ensure that there aren't things that I've gotten wrong.
>
> I'm not accusing you of hiding anything with malice or bad intent.
> Primarilly its your process that is flawed, and its the process that
> needs to be fixed.

As has been stated before we are moving to using the exact same process as=
=20
fedora uses. the buildsystem lives at=20
http://sparc.koji.fedoraproject.org/koji all source lives in=20
cvs.fedoraproject.org the tools and instructions are all published in the=20
fedora wiki. =20

What is not clear is what your intent is.  or what you are doing.=20

Dennis

--nextPart10900366.PSgTyyrJln
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkgWZR8ACgkQkSxm47BaWfcM2wCfThERI06O3pFVZbLyzGj7c5Rg
dU0An0GIoIwPZezQuSoAV3NvzNZN2nyT
=sbkQ
-----END PGP SIGNATURE-----

--nextPart10900366.PSgTyyrJln--

--===============0882158632317921254==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Aurora-sparc-devel mailing list
[email protected]
http://lists.auroralinux.org/mailman/listinfo/aurora-sparc-devel
Aurora FAQ: http://www.ecs.soton.ac.uk/~mas01r/aurorafaq.html
--===============0882158632317921254==--