public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Alexander <wired@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] an update script for the gentoo developer
Date: Wed, 3 Feb 2010 01:40:10 +0200	[thread overview]
Message-ID: <20100202234010.GB9108@fury.skynet> (raw)

[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]

Hello fellow devs,

I've created a script to help me keep my tree/overlays up-to-date,
automatically regenerate metadata, update eix, etc.

It's not anything too sophisticated, but it works for me, so I thought
I'd share it with you guys.

An updated version of the script is available at my gentoo devspace:
http://dev.gentoo.org/~wired/scripts/update

./update -h gives you all available options
edit the script to set the defaults to your liking.

the script expects the following directory structure:

${DATA_DIR}/
      main/
              gentoo-x86/
              gentoo/ (optional)
              gentoo-news/ (optional)
      overlays/
              {various overlays}
      overlays_disabled/
              {overlays not used}
      make.conf
              autogenerated, holds active overlay list
              imported in /etc/make.conf
      ${SCRIPT_OUTPUT}
              if called with -c, all output goes here

the make.conf is sourced in /etc/make.conf and is generated each time
the overlays/ folder gets updated.

the script is constantly improved and I keep the online version
up-to-date. there are some options that diff/fetch the latest version
for you automatically.

I'll probably add a --sync option soon to make it useful on
systems without a CVS checkout.

hopefully some of you will find it useful.

patches and feedback always welcome :)
-- 
Alex Alexander :: wired
Gentoo Developer
www.linuxized.com

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2010-02-02 23:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100202234010.GB9108@fury.skynet \
    --to=wired@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox