On Fri, Dec 20, 2013 at 06:52:49AM -0500, Michael K. Johnson wrote:
> Start by checking out all the source from the CentOS6 import.
> You'll need to add to your conary configuration:
> repositoryMap centos6.rpath.com https://updates.sas.com/conary/
>
> Then, then the command:
> conary rq --install-label=centos6.rpath.com@rpath:centos-6-common | grep
> :source
> shows what's there.
>
> You won't need everything there (we sure don't have to start
> with sblim, pywbem, xe-guest-utilities, cmpi, conary-cim,
> iconfig, kmod-open-vm-tools) but checking out everything
> there will make sure that you have what you do need.
I'm going to take a first pass at sorting out what we'll need
for the bootstrap import. We don't need any guest utilities.
We don't need factories that mention "package creator". We
don't need variant packages named something-conary as we'll be
using the platform versions of those packages.
Brett, please review this list...
That leaves us with only two normal packages:
conary
conary-policy
And a bunch of infrastructure, most of which is because all the
base classes that are built into conary need to be installable
on the system as well.
autopackage
baserequires
buildpackage
capsule
capsule-rpm-import
cpackage
derived
derivedcapsule
distro-policy
factory-capsule-rpm
(remove at least all the package-version-specific exceptions;
Brett probably knows best which to remove, and he and I can
discuss this together)
fileset
group
groupinfo
groupset
package
redirect
userinfo
_______________________________________________
Foresight-devel mailing list
[email protected]
https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
