New Project: pungi - A Fedora release composing tool

[Jesse Keating]

I have started a new project, by the name of Pungi.  This project aims to be a 
tool to compose Fedora releases.  The goals include simplicity of both code 
and interface.  I hope it will be a candidate for the Fedora Project's 
official tool to create user specific composes of Fedora comprising of both 
Core and Extras packages (or just Fedora packages once things merge) as well 
as the tool to compose the official Fedora Project spin of Fedora.  It should 
prove useful to anybody creating a Fedora based distribution as well.  The 
project is GPLv2 licensed.

How it (I hope) works:
  A package list is fed into Pungi, either by comps or some other means.  A 
set of yum repos to find packages in are also fed in.  Pungi will search for 
matching packages in the set of repos and add the package to the download 
list.  The download lost is depclosed (somewhat different than depsolved, no 
local rpmdb involved), all the deps that are pulled in are depclosed, etc...  
The list of packages is then downloaded into a configured cache dir and 
hardlinked into an arch specific dir within a configured destination dir.  
Then anaconda provided tools such as buildinstall, pkgorder, and splittree 
are ran on the directory of packages turning it into an installable tree and 
splitting packages into CD iso sized sets.  Mkisofs would be used to create 
teh CD isos and DVD iso.

  These are the basic steps.  The tool could further be extended to run some 
simple tree sanity to ensure the compose completed correctly, or other post 
processing type things.

How to help:
  The code for this project lives in a public mercurial repository:
      hg clone http://linux.duke.edu/projects/pungi pungi

Write access is via ssh and can be given upon (validated) request.  Discussion 
of the project will make use of the fedora-buildsys-list(a)redhat.com mailing 
list.  There are no web pages (other than the hg-web interface at the above 
URL) currently.  The source includes information about design and some files 
for testing functionality.

Since this is my first 'from scratch' python project, I welcome input not only 
on code content but code design, project layout, etc.. 

Also, even though I work for Red Hat, this is not so much a Red Hat software 
project.  I'm developing this in the community space, a lot on my own time.

-- 
Jesse Keating
Release Engineer: Fedora

[Joe Todaro]

Hmm... so, how will it be different from Yam?
 
http://dag.wieers.com/home-made/yam/

-Joe




Jesse Keating <jkeating(a)redhat.com&gt; 
Sent by: fedora-buildsys-list-bounces(a)redhat.com
10/24/2006 05:53 PM
Please respond to
Discussion of Fedora build system <fedora-buildsys-list(a)redhat.com&gt;


To
fedora-buildsys-list(a)redhat.com, fedora-devel-list(a)redhat.com, 
kickstart-list(a)redhat.com
cc

Subject
New Project: pungi - A Fedora release composing tool






I have started a new project, by the name of Pungi.  This project aims to 
be a 
tool to compose Fedora releases.  The goals include simplicity of both 
code 
and interface.  I hope it will be a candidate for the Fedora Project's 
official tool to create user specific composes of Fedora comprising of 
both 
Core and Extras packages (or just Fedora packages once things merge) as 
well 
as the tool to compose the official Fedora Project spin of Fedora.  It 
should 
prove useful to anybody creating a Fedora based distribution as well.  The 

project is GPLv2 licensed.

How it (I hope) works:
  A package list is fed into Pungi, either by comps or some other means. A 

set of yum repos to find packages in are also fed in.  Pungi will search 
for 
matching packages in the set of repos and add the package to the download 
list.  The download lost is depclosed (somewhat different than depsolved, 
no 
local rpmdb involved), all the deps that are pulled in are depclosed, 
etc... 
The list of packages is then downloaded into a configured cache dir and 
hardlinked into an arch specific dir within a configured destination dir. 
Then anaconda provided tools such as buildinstall, pkgorder, and splittree 

are ran on the directory of packages turning it into an installable tree 
and 
splitting packages into CD iso sized sets.  Mkisofs would be used to 
create 
teh CD isos and DVD iso.

  These are the basic steps.  The tool could further be extended to run 
some 
simple tree sanity to ensure the compose completed correctly, or other 
post 
processing type things.

How to help:
  The code for this project lives in a public mercurial repository:
      hg clone http://linux.duke.edu/projects/pungi pungi

Write access is via ssh and can be given upon (validated) request. 
Discussion 
of the project will make use of the fedora-buildsys-list(a)redhat.com 
mailing 
list.  There are no web pages (other than the hg-web interface at the 
above 
URL) currently.  The source includes information about design and some 
files 
for testing functionality.

Since this is my first 'from scratch' python project, I welcome input not 
only 
on code content but code design, project layout, etc.. 

Also, even though I work for Red Hat, this is not so much a Red Hat 
software 
project.  I'm developing this in the community space, a lot on my own 
time.

-- 
Jesse Keating
Release Engineer: Fedora
[attachment "attnbvg5.dat" deleted by Joe Todaro/Poughkeepsie/IBM] --
Fedora-buildsys-list mailing list
Fedora-buildsys-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

[Jesse Keating]

On Wednesday 25 October 2006 11:08, Joe Todaro wrote:
>  Hmm... so, how will it be different from Yam?
>   
>  http://dag.wieers.com/home-made/yam/ 
Yam builds a local APT/Yum RPM repository from local ISO files, downloaded 
updates, and extra packages from 3rd party repositories. It takes care of 
setting up the ISO files, downloading the RPMs, configuring HTTP access and 
providing PXE/TFTP resources for remote network installations.

There is some similar functionality in that it gathers packages and creates a 
repo.  As far as I can tell, yam doesn't use any anaconda tools to create any 
installable tree.  Rather it duplicates what already exists on isos, and adds 
other packages as other repos in a directory.  Also there is nothing to 
create isos that can be distributed.

Pungi would be used to produce a set of isos and an installable repository 
that yam would work FROM.

-- 
Jesse Keating
Release Engineer: Fedora

[Diogo Franco]

That's a great tool, I was even wondering how to customize a
installation CD or how to create another CD to install my favorite
extras/livna packages without the need for networking on the new PC :)

I'm just learning python, and I think that following a new project
will be great for studies. I'll help when I can.

[Jesse Keating]

On Wednesday 25 October 2006 15:42, Nikolai wrote:
>  I'm just learning python, and I think that following a new
> project
>  will be great for studies. I'll help when I can. 
Great!  I'd recommend subscribing to the fedora-buildsys-list mailing list.

https://www.redhat.com/mailman/listinfo/fedora-buildsys-list

That's where continued discussion of the project will happen.

-- 
Jesse Keating
Release Engineer: Fedora