View previous topic :: View next topic |
Author |
Message |
Brown Eyed Boy Tux's lil' helper
Joined: 08 Jun 2003 Posts: 85 Location: England
|
Posted: Wed Jun 11, 2003 11:12 pm Post subject: GNOME 2 desktop icons |
|
|
Hi. I've been trying to find a way to make desktop icons automatically tidy themselves up, similar to the "line up icons" feature in _that_ other OS. I've seen the "clean up by name" option, but this isn't what I want. Have I missed something or is this just a feature that GNOME doesn't (yet) have? Cheers. |
|
Back to top |
|
|
At0mic n00b
Joined: 11 May 2003 Posts: 43
|
Posted: Wed Jun 11, 2003 11:16 pm Post subject: |
|
|
I know the 2.3.x series has a Keep Aligned option. I guess you'll have to upgrade
There may be a patch floating around for the 2.2.x series, but I'm not sure. |
|
Back to top |
|
|
Brown Eyed Boy Tux's lil' helper
Joined: 08 Jun 2003 Posts: 85 Location: England
|
Posted: Wed Jun 11, 2003 11:29 pm Post subject: |
|
|
Cheers. I think I'll probably be lazy and wait for 2.4 though |
|
Back to top |
|
|
Obz Retired Dev
Joined: 11 Jun 2002 Posts: 274
|
Posted: Thu Jun 12, 2003 2:25 am Post subject: |
|
|
hi,
i'm using stable gnome, and the latest stable nautilus, 2.2.4, which has the 'keep aligned' option, in the desktop menu (right click on your desktop).
hope that helps.
mike. |
|
Back to top |
|
|
tomthewombat Apprentice
Joined: 29 Mar 2003 Posts: 244 Location: NY State
|
Posted: Thu Jun 12, 2003 2:47 am Post subject: |
|
|
yeah the nautilus 2.2.4 ebuild applies a snap to grid patch by default. |
|
Back to top |
|
|
Brown Eyed Boy Tux's lil' helper
Joined: 08 Jun 2003 Posts: 85 Location: England
|
Posted: Thu Jun 12, 2003 4:39 pm Post subject: |
|
|
Cheers. Is the 2.2.4 ebuild in the main portage tree? I'm asking because (after "emerge sync") I get the following
$ emerge --search nautilus
Searching...
[ Results for search key : nautilus ]
[ Applications found : 5 ]
* gnome-base/nautilus
Latest version available: 2.2.3
Latest version installed: 2.2.3
Size of downloaded files: 4,466 kB
Homepage: http://www.gnome.org/projects/nautilus/
Description: A filemanager for the Gnome2 desktop
|
|
Back to top |
|
|
djf_jeff Apprentice
Joined: 17 Feb 2003 Posts: 174 Location: Quebec
|
Posted: Thu Jun 12, 2003 6:10 pm Post subject: |
|
|
emerge -pv /usr/portage/gnome-base/nautilus/nautilus-2.2.4.ebuild
will make the trick! |
|
Back to top |
|
|
Brown Eyed Boy Tux's lil' helper
Joined: 08 Jun 2003 Posts: 85 Location: England
|
Posted: Thu Jun 12, 2003 7:53 pm Post subject: |
|
|
Thanks. So I take it that when multiple versions of the same package exist and the later one is masked (presumably becuase it's unstable), only the unmasked one is returned with an "emerge --search". Is there an option to override this and make "emerge --search" list both the masked and unmasked package versions? |
|
Back to top |
|
|
Obz Retired Dev
Joined: 11 Jun 2002 Posts: 274
|
Posted: Fri Jun 13, 2003 12:37 am Post subject: |
|
|
nautilus 2.2.4 is marked unstable (for x86 at least). unstable packages require you to have selected 'unstable' portage (so to speak), by including
/etc/make.conf
Code: | ACCEPT_KEYWORDS="~x86" |
in terms of _actual_ stability, to me unstable and stable are more labels for "not as well tested" and "better tested". unstable is _unlikely_ to break your system, although it's still possible i guess.
so in short, to always be able to use/search for unstable packages, add the accept keywords line into your /etc/make.conf.
hope that helps. |
|
Back to top |
|
|
lurid Guru
Joined: 12 Mar 2003 Posts: 595 Location: Florida
|
Posted: Fri Jun 13, 2003 1:37 am Post subject: |
|
|
Yeah, but sometimes unstable can mean _seriously_ unstable. In my experience changing /etc/make.conf is a mistake. Especially when you're not paying attention and emerge -u world and install _all_ unstable software.
A better solution is to append ACCEPT_KEYWORDS="~x86" to the begining of something you want to install. That way, everyone knows exactly what they're getting into. |
|
Back to top |
|
|
Odin Tux's lil' helper
Joined: 04 Mar 2003 Posts: 92
|
Posted: Fri Jun 13, 2003 2:38 am Post subject: |
|
|
lurid wrote: | Yeah, but sometimes unstable can mean _seriously_ unstable. In my experience changing /etc/make.conf is a mistake. Especially when you're not paying attention and emerge -u world and install _all_ unstable software.
A better solution is to append ACCEPT_KEYWORDS="~x86" to the begining of something you want to install. That way, everyone knows exactly what they're getting into. |
Is there a way to change the behavior of downgrading everything thats masked when doing an emerge -u world, though? Thats the only 'issue' I've had with doing it this way. Generally I either do that, or just specify the ebuild path. |
|
Back to top |
|
|
lurid Guru
Joined: 12 Mar 2003 Posts: 595 Location: Florida
|
Posted: Fri Jun 13, 2003 4:02 am Post subject: |
|
|
The -U flag means "upgrade only"
emerge -U world
Sometimes this doesn't always work though (its rare, but it happens) which is why you should always stick a -p in there first to see whats going to be down/upgraded. :) |
|
Back to top |
|
|
nertzy n00b
Joined: 08 Jan 2003 Posts: 10 Location: Austin, TX
|
Posted: Sun Jun 15, 2003 9:38 am Post subject: |
|
|
Brown Eyed Boy wrote: | Thanks. So I take it that when multiple versions of the same package exist and the later one is masked (presumably becuase it's unstable), only the unmasked one is returned with an "emerge --search". Is there an option to override this and make "emerge --search" list both the masked and unmasked package versions? |
Sure! Avoid touching /etc/make.conf by typing:
Code: | $ ACCEPT_KEYWORDS="~x86" emerge -s <search term> |
You can do this before any emerge command to change a make.conf setting for that command only. The only trouble I ever have with it is when ACCEPT_KEYWORDS mixes with -u and updates all the dependencies as well unnecessary to unstable versions. |
|
Back to top |
|
|
Odin Tux's lil' helper
Joined: 04 Mar 2003 Posts: 92
|
Posted: Mon Jun 16, 2003 4:26 am Post subject: |
|
|
lurid wrote: | The -U flag means "upgrade only"
emerge -U world
Sometimes this doesn't always work though (its rare, but it happens) which is why you should always stick a -p in there first to see whats going to be down/upgraded. |
Cool thanks.. I always do a -p first.. I didn't notice the difference between U and u I guess. |
|
Back to top |
|
|
Brown Eyed Boy Tux's lil' helper
Joined: 08 Jun 2003 Posts: 85 Location: England
|
Posted: Mon Jun 16, 2003 8:39 pm Post subject: |
|
|
Quote: | Code: |
$ ACCEPT_KEYWORDS="~x86" emerge -s <search term> |
|
Cheers. I've installed masked packages before but I didn't realise that you could use the above with the --search option. Why does the --search option turn up some masked packages?
Quote: | The -U flag means "upgrade only" |
I notice that this isn't documented in the man page (although it is explained in the emerge --help page). I guess the man page needs updating. |
|
Back to top |
|
|
|