[gentoo-user] Layman and eix-sync
Dale
I'm using layman to keep KDE 3.5 installed and have a question. I run
eix-sync to sync my tree. From what I see, it appears it also syncs the
layman part as well. Does it? This is what I see:
[0] "gentoo" /usr/portage/ (cache: metadata-flat)
Reading 100%
[1] "kde-sunset" /usr/local/portage/layman/kde-sunset (cache:
parse|ebuild*#metadata-flat#assign)
Reading 100%
I just want to make sure I am seeing this correctly.
While I am here, I plan to get rid of all the layman stuff when KDE 4 is
ready enough for me to use. Do I just run layman -d all and unmerge
layman? Does that get the job done?
Thanks much.
Dale
:-) :-)
Johannes Kimmel
> Hi,
>
> I'm using layman to keep KDE 3.5 installed and have a question. I run
> eix-sync to sync my tree. From what I see, it appears it also syncs
> the layman part as well. Does it? This is what I see:
>
> [0] "gentoo" /usr/portage/ (cache: metadata-flat)
> Reading 100% [1]
> "kde-sunset" /usr/local/portage/layman/kde-sunset (cache:
> parse|ebuild*#metadata-flat#assign)
> Reading 100%
> I just want to make sure I am seeing this correctly.
--sync". It just rereads the overlay, without "layman -S" in advance.
You have to do that manually.
> While I am here, I plan to get rid of all the layman stuff when KDE 4
> is ready enough for me to use. Do I just run layman -d all and
> unmerge layman? Does that get the job done?
>
> Thanks much.
>
> Dale
>
> :-) :-)
>
Maybe you want install kde4 first and then run "emerge --depclean"
(after removing the overlay). In that way you had an backup if kde4 fails.
Johannes
Alan McKinnon
> Hi,
>
> I'm using layman to keep KDE 3.5 installed and have a question. I run
> eix-sync to sync my tree. From what I see, it appears it also syncs the
> layman part as well. Does it? This is what I see:
>
> [0] "gentoo" /usr/portage/ (cache: metadata-flat)
> Reading 100%
> [1] "kde-sunset" /usr/local/portage/layman/kde-sunset (cache:
> parse|ebuild*#metadata-flat#assign)
> Reading 100%
>
> I just want to make sure I am seeing this correctly.
No, eix-sync does an emerge --sync and updates the local cache for portage and
all overlays trees. To sync the overlays you need this:
layman -S && eix-sync
> While I am here, I plan to get rid of all the layman stuff when KDE 4 is
> ready enough for me to use. Do I just run layman -d all and unmerge
> layman? Does that get the job done?
Leave layman installed, it's useful. You also need it if you want the sunrise
stuff.
Run KDE4 and 3.5 side by side for a bit till you are happy. They use different
directories in ~ so they don't clash:
kde-3.5 ~/.kde
kde-4 ~/.kde4
then unmerge all of kde-3.5, verify with depclean, then delete the overlay
--
alan dot mckinnon at gmail dot com
Dale
> On Thursday 12 November 2009 04:17:47 Dale wrote:
>
>> Hi,
>>
>> I'm using layman to keep KDE 3.5 installed and have a question. I run
>> eix-sync to sync my tree. From what I see, it appears it also syncs the
>> layman part as well. Does it? This is what I see:
>>
>> [0] "gentoo" /usr/portage/ (cache: metadata-flat)
>> Reading 100%
>> [1] "kde-sunset" /usr/local/portage/layman/kde-sunset (cache:
>> parse|ebuild*#metadata-flat#assign)
>> Reading 100%
>>
>> I just want to make sure I am seeing this correctly.
>>
>
> No, eix-sync does an emerge --sync and updates the local cache for portage and
> all overlays trees. To sync the overlays you need this:
>
> layman -S && eix-sync
>
>
I'm wondering if something is set differently here. After running
eix-sync, there were updates from the layman part. I got lines like this:
>>> Fetching (15 of 16) kde-base/konq-plugins-3.5.10 from kde-sunset
>>> Fetching (16 of 16) kde-base/kdeaddons-meta-3.5.10 from kde-sunset
But also some like this:
>>> Fetching (3 of 16) media-libs/libsdl-1.2.13-r1
>>> Fetching (5 of 16) sci-calculators/kconvert-1.1-r1
I haven't changed any configs for layman except to add that one line to
make.conf that tells it where where the source is. This is odd.
>> While I am here, I plan to get rid of all the layman stuff when KDE 4 is
>> ready enough for me to use. Do I just run layman -d all and unmerge
>> layman? Does that get the job done?
>>
>
> Leave layman installed, it's useful. You also need it if you want the sunrise
> stuff.
>
> Run KDE4 and 3.5 side by side for a bit till you are happy. They use different
> directories in ~ so they don't clash:
>
> kde-3.5 ~/.kde
> kde-4 ~/.kde4
>
> then unmerge all of kde-3.5, verify with depclean, then delete the overlay
>
>
I thought they changed all that? I have /usr/kde/3.5 but nothing for
KDE 4. Equery shows this:
root@smoker ~ # equery files kde-base/kdelibs-4.3.3
[ Searching for packages matching kde-base/kdelibs-4.3.3... ]
* Contents of kde-base/kdelibs-4.3.3:
/etc
/etc/xdg
/etc/xdg/menus
/etc/xdg/menus/kde-4.3-applications.menu
/usr
/usr/bin
/usr/bin/checkXML
/usr/bin/kbuildsycoca4
/usr/bin/kconfig_compiler
/usr/bin/kcookiejar4
/usr/bin/kde4-config
/usr/bin/kded4
/usr/bin/kdeinit4
/usr/bin/kdeinit4_shutdown
/usr/bin/kdeinit4_wrapper
/usr/bin/kjs
/usr/bin/kjscmd
/usr/bin/kross
/usr/bin/kshell4
/usr/bin/kunittestmodrunner
/usr/bin/kwrapper4
/usr/bin/makekdewidgets
/usr/bin/meinproc4
/usr/bin/nepomuk-rcgen
/usr/bin/preparetips
I used to have the kdeprefix flag set but they masked it.
I do have both KDE 3.5 and KDE 4 installed. It's just that some things
don't work in KDE 4 yet. I like it but I still use KDE 3.5 for the most
part. We been discussing this on the KDE list.
I'm just not a real big fan of this layman thing, yet anyway. It may
grow on me. Who knows.
Dale
:-) :-)
Daniel Pielmeier
>
> I'm wondering if something is set differently here. After running eix-sync,
> there were updates from the layman part. I got lines like this:
>
>>>> Fetching (15 of 16) kde-base/konq-plugins-3.5.10 from kde-sunset
>>>> Fetching (16 of 16) kde-base/kdeaddons-meta-3.5.10 from kde-sunset
>
> But also some like this:
>
>>>> Fetching (3 of 16) media-libs/libsdl-1.2.13-r1
>>>> Fetching (5 of 16) sci-calculators/kconvert-1.1-r1
>
> I haven't changed any configs for layman except to add that one line to
> make.conf that tells it where where the source is. This is odd.
>
You can edit /etc/eix-sync.conf to sync layman overlays with eix-sync.
I think adding a line with "*" there should be enough, but look up the
eix man page to be sure.
This way eix-sync does the following emerge --sync && layman -S && eix-update.
--
Daniel Pielmeier
Frank Steinmetzger
> Alan McKinnon wrote:
>>> While I am here, I plan to get rid of all the layman stuff when KDE 4 is
>>> ready enough for me to use. Do I just run layman -d all and unmerge
>>> layman? Does that get the job done?
>>
>> Leave layman installed, it's useful. You also need it if you want the
>> sunrise stuff.
>>
>> Run KDE4 and 3.5 side by side for a bit till you are happy. They use
>> different directories in ~ so they don't clash:
>>
>> kde-3.5 ~/.kde
>> kde-4 ~/.kde4
The only "clash" I experience is that a kbuildsyoca (without the 4) in kde4
environment causes kde3 quicklauncher to lose all contents except for the
Kontact symbol, kcontrol becomes empty and nothing from the k-menu works. If I
do the kbuildsycoca back in kde3, then log out and in again, everything is back
to normal, only the Quicklauncher remains empty. I got used to it thanks to
Katapult. :-)
>> then unmerge all of kde-3.5, verify with depclean, then delete the
>> overlay
>>
>
> I thought they changed all that? I have /usr/kde/3.5 but nothing for KDE
> 4. Equery shows this:
> root@smoker ~ # equery files kde-base/kdelibs-4.3.3
Alan spoke about the configs and app data in ~. kdelibs naturally installs into
the system, not home. And if you don't enable the prefix useflag in the older
version (I believe they removed it a while ago anyway), then it installs HFS
compliantly into /usr instead of /usr/kde/$version.
PS.: I too use the kde3 overlay, as I am hesitant to switch as well. The bloody
NVidia graphics driver causes regular flickering and sometimes it all hangs. I
have orphaned entries in the task panel on a regular basis. KDM4 doesn't like
my preferred font size. And until the Akregator devs have dealt with
https://bugs.kde.org/show_bug.cgi?id=190616 I can't use Kontact 4 either.
--
Am 8. Tag schuf Gott das Bier, und seitdem h�rte man nichts mehr von ihm.
Alan McKinnon
> >> then unmerge all of kde-3.5, verify with depclean, then delete the
> >> overlay
> >
> > I thought they changed all that? I have /usr/kde/3.5 but nothing for KDE
> > 4. Equery shows this:
>
> > root@smoker ~ # equery files kde-base/kdelibs-4.3.3
>
> Alan spoke about the configs and app data in ~. kdelibs naturally installs
> into the system, not home. And if you don't enable the prefix useflag in
> the older version (I believe they removed it a while ago anyway), then it
> installs HFS compliantly into /usr instead of /usr/kde/$version.
>
Correct.
KDE-3.5 installs into /usr/kde3.5/
KDE-4 installs into /usr/
with kdeprefix, KDE-4 *used* to install into /usr/kde4.1, /usr/kde4.2, etc but
this was a bad idea when it started and never got any better so it was canned.
Full gory details in the KDE4 docs on gentoo.org.
Short version: Do not use kdeprefix. Ever.
Dale
I wasn't thinking about the /home config but the KDE install itself.
Now we are on the same page. I see more clearly now. They did
mask/disable the kdeprefix USE flag. It's not a "option" anymore.
There is a lot that I like about KDE 4 but it just isn't quite usable
for everything I do just yet. It's getting there tho.
Dale
:-) :-)
James Ausmus
2009/11/12 Dale <rdale...@gmail.com>:
>You can edit /etc/eix-sync.conf to sync layman overlays with eix-sync.
> I'm wondering if something is set differently here. After running eix-sync,
> there were updates from the layman part. I got lines like this:
>
>>>> Fetching (15 of 16) kde-base/konq-plugins-3.5.10 from kde-sunset
>>>> Fetching (16 of 16) kde-base/kdeaddons-meta-3.5.10 from kde-sunset
>
> But also some like this:
>
>>>> Fetching (3 of 16) media-libs/libsdl-1.2.13-r1
>>>> Fetching (5 of 16) sci-calculators/kconvert-1.1-r1
>
> I haven't changed any configs for layman except to add that one line to
> make.conf that tells it where where the source is. This is odd.
>
I think adding a line with "*" there should be enough, but look up the
eix man page to be sure.
That's correct - all you need is a single line with an asterisk on it:
*
-James
Dale
>
> 2009/11/12 Dale <rdale...@gmail.com <mailto:rdale...@gmail.com>>:
Like this:
root@smoker ~ # cat /etc/eix-sync.conf
*
root@smoker ~ #
I synced a bit ago so it may be a day or two before I sync again.