-vanilla builds.

[Dave Jones]

I'd like to move forward on us getting vanilla builds out for testers.
There are a couple things worth thinking about, which I'd like other
peoples thoughts on.

* The location of the binaries - I think we ended up settling
  on putting them on people.fedoraproject.org.
  Given the 150MB quota, this probably means...
  - no -debuginfo packages. (not a huge deal)
  - probably just x86/x86-64 to begin with.
  - probably no non-debug variants (ie, same model
    as rawhide, with debug 'always on'
  - worth doing PAE and non-PAE ? just one? which?

* how/where to building them.
  AFAIK, it isn't possible to pass switches like --with-vanilla
  to koji, so the two options are..
  - build vanilla as part of the regular build
    (not a great idea, it already takes hours to build
     a complete set of kernels).
  - I kick off a bunch of rpmbuilds locally and push them
    by hand. (scriptable at least, so not such a big deal).
    I think this is the best option.

* frequency of updates.
  I don't think it's really worthwhile doing daily builds.
  Doing at least one per -rc is probably a good target,
  with perhaps a -rcN-git build periodically if the next
  -rc is taking a while to land.

* dependancies.
  This is the only remaining technical puzzle I think.
  I'd like the vanilla rpms to install on FC6, F7, and rawhide.
  Doing separate builds per distro is just going to kill me.
  The only thing stopping this from working is requires: lines
  like ..
  %define kernel_prereq  fileutils, module-init-tools, initscripts >= %8.11.1-1, mkinitrd >= 6.0.9-7

  I'm thinking perhaps something like..
  
  %if ! %{with_vanilla}
  %define kernel_prereq  fileutils, module-init-tools, initscripts >= %8.11.1-1, mkinitrd >= 6.0.9-7
  %else
  %define kernel_prereq  fileutils, module-init-tools, initscripts, mkinitrd
  %endif

  might do the trick.
  However for some cases, those versioned dependancies are there for a reason, and I'm
  not entirely sure what to do about them.  I'd rather not have to
  build non-kernel packages for the vanilla repo too.
  Ideas ?

Ideally I'd like to get to a state where these are built
by a cronjob on my desktop that checks for a new rc,
and uploads new updates whilst I sleep^Wdo something else.

	Dave

-- 
http://www.codemonkey.org.uk