From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question
Date: Sun, 16 Aug 2009 23:33:33 +0200 [thread overview]
Message-ID: <200908162333.33798.volkerarmin@googlemail.com> (raw)
In-Reply-To: <200908162318.40770.alan.mckinnon@gmail.com>
On Sonntag 16 August 2009, Alan McKinnon wrote:
> On Sunday 16 August 2009 23:09:41 Volker Armin Hemmann wrote:
> > On Sonntag 16 August 2009, Alan McKinnon wrote:
> > > On Sunday 16 August 2009 21:46:02 Volker Armin Hemmann wrote:
> > > > On Sonntag 16 August 2009, Alan McKinnon wrote:
> > > > > On Sunday 16 August 2009 21:12:30 Dirk Heinrichs wrote:
> > > > > > Am Sonntag 16 August 2009 21:02:50 schrieb Roy Wright:
> > > > > > > So for the kde-4.3 upgrade, it looks like this is what will be
> > > > > > > necessary:
> > > > > > >
> > > > > > > 1) grab the sets again from the kde-testing overlay and put
> > > > > > > them in / etc/portage/sets (assumption is to do a replace). 2)
> > > > > > > unmerge kde-4.2 using: emerge --unmerge @kde-4.2
> > > > > > > 3) merge kde-4.3 using: emerge -av @kde-4.3
> > > > > > > 4) recustomize kde as the ~/.kde will not be migrated
> > > > > > >
> > > > > > > Am I on the right track?
> > > > > >
> > > > > > No.
> > > > > >
> > > > > > 1) They're in portage.
> > > > >
> > > > > He's asking about the set files, not the ebuilds.
> > > >
> > > > and you don't copy the set files.
> > >
> > > Which set files does one not copy, and why?
> >
> > you don't copy any set files because there is no reason to do so?
>
> And if the changes between kde-4.2 and kde-4.3 DO require changes to the
> set files to build everything, then what should one do? Not copy the files
> and live with the omission/breakage?
>
> Set files do not ship with a --sync, the user must either get them from
> somewhere or create them himself. And additions to 4.3 are not present in
> 4.2, so I don't understand your position. Seems to me that copying working
> set files from somewhere is a requirement in this case, especially if the
> user uses versioned set files.
you install kde-testing. Suddenly you have all the set files needed. you have
all the unmask files needed. You have all keyword files needed.
And the overlay is not that big.
next prev parent reply other threads:[~2009-08-16 21:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-16 19:02 [gentoo-user] upgrading ~x68 kde-4.2 to kde-4.3 question Roy Wright
2009-08-16 19:12 ` Dirk Heinrichs
2009-08-16 19:26 ` Dirk Heinrichs
2009-08-26 7:25 ` Helmut Jarausch
2009-08-26 7:40 ` Alan McKinnon
2009-08-26 7:48 ` Dale
2009-08-26 9:23 ` Helmut Jarausch
2009-08-26 9:54 ` Dale
2009-08-26 10:08 ` Helmut Jarausch
2009-08-26 10:10 ` Alan McKinnon
2009-08-26 16:31 ` Dirk Heinrichs
2009-08-16 19:29 ` Alan McKinnon
2009-08-16 19:46 ` Volker Armin Hemmann
2009-08-16 20:48 ` Alan McKinnon
2009-08-16 21:09 ` Volker Armin Hemmann
2009-08-16 21:18 ` Alan McKinnon
2009-08-16 21:33 ` Volker Armin Hemmann [this message]
2009-08-16 22:12 ` Roy Wright
2009-08-17 5:37 ` Dirk Heinrichs
2009-08-17 22:40 ` [gentoo-user] [solved] " Roy Wright
2009-08-17 5:44 ` [gentoo-user] " Dirk Heinrichs
2009-08-19 18:39 ` Alex Schuster
2009-08-19 21:56 ` John H. Moe
2009-08-19 22:44 ` Alex Schuster
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=200908162333.33798.volkerarmin@googlemail.com \
--to=volkerarmin@googlemail.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