public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirk Heinrichs <dirk.heinrichs.ext@nsn.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update svn ebuilds only when necessary
Date: Mon, 3 Nov 2008 13:52:48 +0100	[thread overview]
Message-ID: <200811031352.50045.dirk.heinrichs.ext@nsn.com> (raw)
In-Reply-To: <20081103121702.GA31249@revolver>

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

Am Montag 03 November 2008 13:17:02 schrieb ext Momesso Andrea:

> Is there a way to to update svn packages only when there are updates in
> the svn source?

No.

> Actually I use a script to grep "9999" from eix -I output and put all
> those packages in a package set, then I have a cron job to rebuild this
> set weekly.

paludis --dl-reinstall-scm weekly

> What I'd like to do is to only fetch the svn sources, and rebuild the
> packages if sources have been updated since last build, saving lots of
> compilations.

After a week, you can usually be sure that sources have changed :-) You can 
use ccache to save compilations.

> Does portage (or any other tool) provide a way to do it?

See above.

HTH...

	Dirk
-- 
Dirk Heinrichs          | Tel:  +49 (0)162 234 3408
Configuration Manager   | Fax:  +49 (0)211 47068 111
Capgemini Deutschland   | Mail: dirk.heinrichs@capgemini.com
Wanheimerstraße 68      | Web:  http://www.capgemini.com
D-40468 Düsseldorf      | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-11-03 12:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 12:17 [gentoo-user] Update svn ebuilds only when necessary Momesso Andrea
2008-11-03 12:21 ` Markos Chandras
2008-11-03 12:36 ` Alan McKinnon
2008-11-03 12:52 ` Dirk Heinrichs [this message]
2008-11-03 13:19   ` Dirk Heinrichs
2008-11-03 13:14 ` Albert Hopkins

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=200811031352.50045.dirk.heinrichs.ext@nsn.com \
    --to=dirk.heinrichs.ext@nsn.com \
    --cc=gentoo-user@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