Mailing List Archive

[kde-sunset] cmake porting status for Trinity
Hello,

Until now, I ported to cmake following packages:

tqtinterface (commited)
arts (commited)
kdelibs (commited)
kdebase
kdepim (partial, only kmail and deps)
kdemultimedia (partial, only kmix)
knetworkmanager
amarok (commited)

The packages marked as "commited" are commited to official Trinity svn
repository( http://websvn.kde.org/branches/trinity/ ).

http://www.thel.ro (tarballs with cmake files)
https://github.com/serghei/kde-trinity (quick and dirty gentoo portage)

--
Serghei
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
Hi Serghei,

On Saturday 15 January 2011 14:52:38 Serghei Amelian wrote:
> Hello,
>
> Until now, I ported to cmake following packages:
>
> tqtinterface (commited)
> arts (commited)
> kdelibs (commited)
> kdebase
> kdepim (partial, only kmail and deps)
> kdemultimedia (partial, only kmix)
> knetworkmanager
> amarok (commited)
>
> The packages marked as "commited" are commited to official Trinity svn
> repository( http://websvn.kde.org/branches/trinity/ ).
>
> http://www.thel.ro (tarballs with cmake files)
> https://github.com/serghei/kde-trinity (quick and dirty gentoo portage)

That is good news, thank you very much for your work!
Is there anything i can help you with ?
I have some coding knowledge, but no idead about cmake...

I hope to be able to test it soon...

greetings,
Roman

--
Many people feel that if you won't let them make you happy, they'll make you
suffer.
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
On Saturday 22 January 2011 09:23:36 Roman wrote:

[...]

> > http://www.thel.ro (tarballs with cmake files)
> > https://github.com/serghei/kde-trinity (quick and dirty gentoo portage)
>
> That is good news, thank you very much for your work!
> Is there anything i can help you with ?
> I have some coding knowledge, but no idead about cmake...

At this time would be great if someone will start using my quick and dirty
ebuilds for creating a more "official" ebuilds. We need an official overlay
and a host for distfiles.

> I hope to be able to test it soon...
>
> greetings,
> Roman



--
Serghei
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
Hi,

On Saturday 22 January 2011 12:51:59 Serghei Amelian wrote:
> On Saturday 22 January 2011 09:23:36 Roman wrote:
>
> [...]
>
> > > http://www.thel.ro (tarballs with cmake files)
> > > https://github.com/serghei/kde-trinity (quick and dirty gentoo portage)
> >
> > That is good news, thank you very much for your work!
> > Is there anything i can help you with ?
> > I have some coding knowledge, but no idead about cmake...
>
> At this time would be great if someone will start using my quick and dirty
> ebuilds for creating a more "official" ebuilds. We need an official overlay
> and a host for distfiles.
>
Testing the ebuilds i was only able to fetch a handful of distfiles.
If you (is thel.ro yours?) could add an rsync-user i would setup a cronjob to
sync the files and you could add that to thirdpartymirrors so emerge would
fetch randomly from both?

greetings,
Roman

--
Entropy isn't what it used to be.
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
On Friday 28 January 2011 10:45:01 Roman wrote:
[...]

> Testing the ebuilds i was only able to fetch a handful of distfiles.
> If you (is thel.ro yours?) could add an rsync-user i would setup a cronjob
> to sync the files and you could add that to thirdpartymirrors so emerge
> would fetch randomly from both?

rsync -avR --delete thel.ro::distfiles /tmp/distfiles
rsync -avR --delete thel.ro::overlay /tmp/overlay

> greetings,
> Roman

--
Serghei
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
On Friday 28 January 2011 11:25:35 Serghei Amelian wrote:
> On Friday 28 January 2011 10:45:01 Roman wrote:
> [...]
>
> > Testing the ebuilds i was only able to fetch a handful of distfiles.
> > If you (is thel.ro yours?) could add an rsync-user i would setup a
> > cronjob to sync the files and you could add that to thirdpartymirrors so
> > emerge would fetch randomly from both?
>
> rsync -avR --delete thel.ro::distfiles /tmp/distfiles
> rsync -avR --delete thel.ro::overlay /tmp/overlay

I did set up the daily cronjob to check thel.ro for new files. The mirror is
available via http:///mirror.hasnoname.de/kde-trinity/


Although i don't really know what i should do with the overlay-files... do you
want me to set it up in a git or something?

To spread the load randomly between thel.ro and hasnoname.de:
create overlay/profiles/repo_name containing overlay-name (i chose
kde-trinity, but it's yours so you decicde).

then you can create overlay/profiles/thirdpartymirrors containing 1 single
line with the following:

overlay-name http://mirror.hasnoname.de/kde-trinity/distfiles
http://www.thel.ro/distfiles/

Afterward you can use SRC_URI="mirror://overlay-name/${P}.tar.bz2" in the
ebuild. Portage will then fetch from official mirrors and fallback to one of
the thirdpartymirrors.

greetings,
Roman

--
We are Pentium of Borg. Division is futile. You will be approximated.
-- seen in someone's .signature
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
On Friday 28 January 2011 11:25:35 Serghei Amelian wrote:
> On Friday 28 January 2011 10:45:01 Roman wrote:
> [...]
>
> > Testing the ebuilds i was only able to fetch a handful of distfiles.
> > If you (is thel.ro yours?) could add an rsync-user i would setup a
> > cronjob to sync the files and you could add that to thirdpartymirrors so
> > emerge would fetch randomly from both?
>
> rsync -avR --delete thel.ro::distfiles /tmp/distfiles
> rsync -avR --delete thel.ro::overlay /tmp/overlay
>
> > greetings,
> > Roman

I did set up the daily cronjob to check thel.ro for new files. The mirror is
available via http:///mirror.hasnoname.de/kde-trinity/
Overlay: http://git.hasnoname.de/kde-trinity

To spread the load randomly between mirrors:
create overlay/profiles/repo_name containing overlay-name (i chose
kde-trinity, but it's yours so you decicde).

then you can create overlay/profiles/thirdpartymirrors containing 1 single
line with the following:

overlay-name http://mirror.hasnoname.de/kde-trinity/distfiles
http://www.thel.ro/distfiles/

Afterward you can use SRC_URI="mirror://overlay-name/${P}.tar.bz2" in the
ebuild. Portage will then fetch from official mirrors and fallback to one of
the thirdpartymirrors.

I attached a patch containing initial fixups:
-changed KEYWORDS to ~x86 ~amd64
-added my host as thirdpartymirror
-rebuild manifests since i got lots of manifests errors


greetings,
Roman

--

Dasher, Dancer ... Prancer ... Nixon, Comet, Cupid ... Donna Dixon.

-- Homer Simpson
Simpsons Roasting on an Open Fire
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
Hi again,

Am Saturday 29 January 2011 10:42:53 schrieben Sie(Serghei Amelian
<serghei@thel.ro>):
> > Although i don't really know what i should do with the overlay-files...
> > do you want me to set it up in a git or something?
> Sure, would be nice.
Ok, i set up a git repo at
http://git.hasnoname.de/Overlays/kde-trinity
git://git.hasnoname.de/Overlays/kde-trinity

Already made some changes to the ebuilds (mostly dependencies), but still not
useable..

> Actually I want to pass ebuilds development to Gentoo people, because I'm
> pretty bussy with cmake and other Trinity things. Also, I'm not exactly an
> portage guru and my ebuilds are pretty sloppy (I think it needs some
> rework).
Thats totally understandable, i will try to get a working desktop from your
ebuilds, but it looks like it is still a lot of work to do.
i still have to edit files by hand to get to a desktop and then i get en empty
K-Menu, guess i will have to take a closer look at the old ebuilds. Also it
seems kdm is crashing every time...
As i am not an expert on this.. if anybody wants to get it working... just
send me a mail..

greetings,
Roman

--
Make headway at work. Continue to let things deteriorate at home.
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
On Friday 04 February 2011 10:27:05 Roman wrote:
[...]
> Thats totally understandable, i will try to get a working desktop from your
> ebuilds, but it looks like it is still a lot of work to do.
> i still have to edit files by hand to get to a desktop and then i get en
> empty K-Menu, guess i will have to take a closer look at the old ebuilds.

kmenu appear empty because XDG variable environments. Set it correctly then
run kbuildsycoca (while kde session running).

> Also it seems kdm is crashing every time...
> As i am not an expert on this.. if anybody wants to get it working... just
> send me a mail..

I was made a quick and dirty hack to get working kdm (prepend follow commands
to /usr/kde/3.5/share/config/kdm/Xsession):

source /etc/profile
export XDG_CONFIG_DIRS="/usr/kde/3.5/etc/xdg:$XDG_CONFIG_DIRS"
export XDG_DATA_DIRS="/usr/kde/3.5/share:$XDG_DATA_DIRS"
export LD_LIBRARY_PATH="/usr/kde/3.5/lib"
export PATH="/usr/kde/3.5/bin:$PATH"

/usr/kde/3.5/bin/startkde
exit 0


I think this must be fixed in upstream, sometime.

http://bugs.pearsoncomputing.net/show_bug.cgi?id=421

> greetings,
> Roman

--
Serghei
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
On Friday 04 February 2011 09:44:18 Serghei Amelian wrote:
> On Friday 04 February 2011 10:27:05 Roman wrote:
> [...]
>
> > Thats totally understandable, i will try to get a working desktop from
> > your ebuilds, but it looks like it is still a lot of work to do.
> > i still have to edit files by hand to get to a desktop and then i get en
> > empty K-Menu, guess i will have to take a closer look at the old ebuilds.
>
> kmenu appear empty because XDG variable environments. Set it correctly then
> run kbuildsycoca (while kde session running).
Yes, thought so... need to look at the gentoo-specific variables and
startup-files.

> I was made a quick and dirty hack to get working kdm (prepend follow
> commands to /usr/kde/3.5/share/config/kdm/Xsession):
> source /etc/profile
> export XDG_CONFIG_DIRS="/usr/kde/3.5/etc/xdg:$XDG_CONFIG_DIRS"
> export XDG_DATA_DIRS="/usr/kde/3.5/share:$XDG_DATA_DIRS"
> export LD_LIBRARY_PATH="/usr/kde/3.5/lib"
> export PATH="/usr/kde/3.5/bin:$PATH"
>
> /usr/kde/3.5/bin/startkde
> exit 0
> I think this must be fixed in upstream, sometime.
>
> http://bugs.pearsoncomputing.net/show_bug.cgi?id=421
Thx, will try that and work on the files over the weekend...

Just another question: where should i put cmake-related fixes, that
could/should be fixed? Send them to you? Or is there sth. on the
trinity-pages that i couldn't find...?
(in this case i think the avahi-dependency in CMakeList.txt could be
optional).

greetings,
Roman

--
Information Processing:
What you call data processing when people are so disgusted with
it they won't let it be discussed in their presence.
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
On Saturday 05 February 2011 11:41:01 Roman wrote:

[...]

> Just another question: where should i put cmake-related fixes, that
> could/should be fixed? Send them to you? Or is there sth. on the
> trinity-pages that i couldn't find...?

If you have patches, send it to me, I will commit it to trinity svn.

> (in this case i think the avahi-dependency in CMakeList.txt could be
> optional).

I'm not sure that kdelibs can be compiled without avahi, as I understand avahi
are mandatory at this time. I will ask Tim.

> greetings,
> Roman

PS You can reach me at chat.freenode.net, channel #trinity-desktop

--
Serghei
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
hi serghei,

i can't mail you directly, serghei@thel.ro gives "Access denied"...

i wanted to get back to you much sooner, but i currently have a very busy
personal life. So i probably can't check in on irc..

As we talked on irc, i did some work on the ebuilds (not yet commited to
github).
As i was trying to bump some ebuilds to a newer revision, i stumbled across a
little problem.
In the trinity-svn there is the kde-common/cmake folder which seems to be
needed by every ebuild as it contains some tqt/TDE files.

When you packaged the distfiles did you just copy cmake to kdebase/cmake or
did you have to change anything else?

Does the trinity-svn contain basically the same cmake-related files as your
tarballs?

I am currently working on a script to bump the ebuilds/automatically create
the tarballs from svn and am thinking to package kde-common/cmake into its
own archive and add -DCMAKE_SOURCE_DIR=workdir/cmake to the ebuilds, if that
is all that is needed.

Still need to find out why kdm keeps segfaulting and how to get desktop
configured automatically (guess that is part of the startkde-script which i
will have to gentooify).

If my tests go well, i think i can commit the stuff at the end of the week..


greetings,
Roman

--
It's been my observation that a person's brains get evenly divided up
among their sockpuppets.
From: Alan Connor
Re: [kde-sunset] cmake porting status for Trinity [ In reply to ]
On Tuesday 22 February 2011 11:16:50 Roman wrote:
> hi serghei,
>
> i can't mail you directly, serghei@thel.ro gives "Access denied"...

My s25r filter... :) I white-listed you.

[...]

> When you packaged the distfiles did you just copy cmake to kdebase/cmake or
> did you have to change anything else?

Don't worry about this, kde-common/cmake is an svn external dependecy and is
downloaded automatically.

--
Serghei