(This patch was merged in 080bf584 .)

... where "selective" means | head -1.  Some pythons spew not only their
version but also the compiler version, so we were getting a multi-line
value for PYTHON_VERSION in some places, which breaks the generated
GNUMakefiles.  configure must be setting some env var that is causing
newer or custom-built pythons to produce this extra information.
Anyway, head -1 should be a fine strategy.

alpine tcsh package moved to community branch

See merge request !41

The alpine tcsh package has been moved from the testing
repository of packages to the community one. Since we use
it need a small update to where we're sourcing it from so
we can continue to install it and build its dependencies.

1. The primary change is to the Create Image modal; we now allow users
   to optionally specify a description for the image. This needed to be
   plumbed through all the way to the GeniCM CreateImage() API. Since
   the modal is getting kinda overloaded, I rearranged things a bit and
   changed the argument checking and error handling. I think this is the
   limit of what we want to do on this modal, need a better UI in the
   future.

2. Of course, if we let users set descriptions, lets show them on the
   image listing page. While I was there, I made the list look more like
   the classic image list; show the image name and project, and put the
   URN in a tooltip, since in general the URN is noisy to look at.

3. And while I was messing with the image listing, I noticed that we
   were not deleting profiles like we said we would. The problem is that
   when we form the image list, we know the profile versions that can be
   deleted, but when the user actually clicks to delete, I was trying to
   regen that decision, but without asking the cluster for the info
   again. So instead, just pass through the version list from the web
   UI.

is readable, since its on boss, this is fine.

based slices.

Everybody's doing it!

Cuz you can never have too many sitevars!

description in CreateImage();

running.

hand). Also add enable sitevar since we run this only on clusters that
support portstats on the control network.

easily get to the experiment (or portal status page).

Portal) that the experiment was created on.

* Add portal url to the existing emulab extension that tells the CM the
  CreateSliver() is coming from the Portal. Always send this info, not
  just for the Emulab Portal.

* Stash that info in the geni slice data structure so we can add links
  back to the portal status page for current slices.

* Add routines to generate a portal URL for the history entries, since
  we will not have those links for historical slices. Add links back to
  the portal on the showslice and slice history pages.

manifest we have store in the DB. Basically a highly stripped down
version of the status page.

IPs on the lan and we fill them in, we put those IPs into the manifest,
but we also have to put the netmask in, since without that, the update
operation will get confused.

if the underlying Emulab experiment; return a busy error instead.