public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <gentoo-user@devrieze.net>
To: Alexander Gretencord <arutha@gmx.de>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] portage question
Date: Wed, 2 Oct 2002 11:12:35 +0200	[thread overview]
Message-ID: <200210021112.35560.gentoo-user@devrieze.net> (raw)
In-Reply-To: <200210021102.42324.arutha@gmx.de>

On Wednesday 02 October 2002 11:02, Alexander Gretencord wrote:
>
> Now lets say we want to update our kernel from gentoo-sources-2.4.18 to
> gentoo-sources-2.4.19-r7. Portage sees there's already a
> linux-2.4.18.tar.bz2 so we don't download the linux-2.4.19.tar.bz2 from
> kernel.org but instead download the patch from 2.4.18 to 2.4.19, unpack the
> 2.4.18 into our new directory, patch it to 2.4.19 and then patch in the
> stuff that makes a gentoo-sources-r7 out of it.
>
> I don't see where this would be a problem either with the kernel or any
> other package. Of course you'd need quite some patches on the servers for
> that thats true :)
>
> No, don't build it into the ebuilds, let portage do it. The ebuild has
> nothing to do with it!
>

I wish it was so simple. The only way that portage is going to know about 
patches is when we tell portage about them. This would involve some file that 
describes how to get from source 1 to source 2. It also only would work when 
the ebuild doesn't explicitly unpack the source file. 

In short this is very complex and not really supported by portages original 
design. It would be nice though, but at the moment there are more important 
things to do for portage.

Paul

-- 
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net



  reply	other threads:[~2002-10-02  9:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 23:09 [gentoo-dev] portage question Leon Chiver
2002-10-02  7:22 ` Henti Smith
2002-10-02  7:39   ` Evan Read
2002-10-02  9:02     ` Alexander Gretencord
2002-10-02  9:12       ` Paul de Vrieze [this message]
2002-10-02 12:28         ` Toby Dickenson
2002-10-02 12:34         ` Toby Dickenson
2002-10-02 10:06       ` Henti Smith
2002-10-02 11:53         ` Christian Skarby
2002-10-02 11:54           ` Henti Smith
2002-10-02 12:23             ` Christian Skarby
2002-10-02 12:26               ` Henti Smith
2002-10-02 14:12               ` Alexander Gretencord
2002-10-02 14:11         ` [gentoo-dev] " Leon Chiver
2002-10-03  9:10           ` Paul de Vrieze
  -- strict thread matches above, loose matches on Subject: below --
2001-08-25 15:26 [gentoo-dev] Portage question Christopher Burgess
2001-08-25 15:36 ` Mikael Hallendal
2001-08-25 14:57 Christopher Burgess
2001-08-25 15:06 ` Mikael Hallendal
2001-08-25 15:20   ` Daniel Robbins
2001-08-25 15:32     ` Mikael Hallendal
2001-08-27  8:48 ` Djamil ESSAISSI
2001-01-30 21:23 [gentoo-dev] useradd q Dave Bresson
2001-01-30 21:57 ` Achim Gottinger
2001-01-30 23:14   ` [gentoo-dev] portage question John McCaskey

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=200210021112.35560.gentoo-user@devrieze.net \
    --to=gentoo-user@devrieze.net \
    --cc=arutha@gmx.de \
    --cc=gentoo-dev@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