View previous topic :: View next topic |
Author |
Message |
gionnico Apprentice
Joined: 29 Jun 2007 Posts: 192 Location: Italy
|
Posted: Sun Aug 24, 2008 9:23 am Post subject: [portage 2.2] Only emerge *new* packages for a set |
|
|
I've got the problem that the @kde-svn set is inconstistent.
So the emerge often stops when a package doesn't compile.
I have to "emerge @kde-svn" again but it also wants to reinstall all the already installed packages. Can I avoid this behaviour? |
|
Back to top |
|
|
MalleRIM Guru
Joined: 23 Jul 2007 Posts: 563 Location: China
|
Posted: Sun Aug 24, 2008 9:33 am Post subject: |
|
|
try emerge -u
portage can't detect if scm packages were updated though. |
|
Back to top |
|
|
gionnico Apprentice
Joined: 29 Jun 2007 Posts: 192 Location: Italy
|
Posted: Sun Aug 24, 2008 9:39 am Post subject: |
|
|
MalleRIM wrote: | try emerge -u
portage can't detect if scm packages were updated though. |
Are you using an eeePC?
I know but if a svn compiled once it's just ok for now - until I make KDE work. There's time, later, to update.
I'll try - but that "--update" should only update packages and "New" packages should be untouched.
If not "emerge --uDN world" would install the "world".
edit: however, it works. With "emerge --resume --skipfirst" I had lost 10 packages. |
|
Back to top |
|
|
yngwin Retired Dev
Joined: 19 Dec 2002 Posts: 4572 Location: Suzhou, China
|
Posted: Sun Aug 24, 2008 6:33 pm Post subject: |
|
|
Code: | emerge @kde-svn --noreplace --keep-going |
_________________ "Those who deny freedom to others deserve it not for themselves." - Abraham Lincoln
Free Culture | Defective by Design | EFF |
|
Back to top |
|
|
|