Daily KDE4 Subversion Packages

markc · 2009-08-18 06:03:14

@atomopawn: hmm, I'm sure that section has been commented out for quite some time, see http://github.com/markc/kde-svn/raw/mas … t/PKGBUILD

OIC, you mean you are building directly from Git instead of the "old" KDE svn repo. I suspect you are using my old source packages from Google Code, is that possible?

If so then mv you current source package dir to whatever_old and git clone git@github.com:markc/kde-svn.git, assuming your ssh key is set up right, and feel free to update the source packages. As I indicated in my previous post, my first attempt to pull from the new Git source tree failed (for kde-qt). Also, kdebase was not building for the last week because it was missing integrity checks from the new stricter pacman v3.3. I have absolutely no idea what the state of the KDE move from svn to git is atm.

Oops, to answer your question, no, the VLC stuff is not important but it's probably worth leaving in but commented in case it's worth another try at some point.

atomopawn · 2009-08-18 07:03:54

markc: Thanks for your quick reply.

I am using your current git tree. The code I had to comment out is above the block that's commented out in the link you posted. My problem is that there is no $SRCDEST/playground/multimedia directory on my system, so the PKGBUILD fails. Maybe I just need to install things in a different order.

markc · 2009-08-18 10:01:37

@atomopawn: ah, I see what you mean. Actually you may as well cut all the VLC stuff out because I can get it back as a git diff sometime in the future if I am inclined to try it again. See if you can push your changes through to github.

Some thoughts; if anyone is interested, I think the best way to keep the daily svn/git builds alive is if there is a better system to keep them updated and gitorious.org has the concept of "teams" so how about we (not just me) come up with a new name for the Git version of this package set and set up a new repo on gitorious (where Qt is, and KDE will be) and kind of start from scratch. It's quite easy for me to keep building and hosting the binaries, until someone else wants to take over, but it worries me about keeping them uptodate and tested as it's an all round waste of everyones time if the binary packages don't get any care and attention and cause more problems than what they're worth. The only thing from my point of view is that I do not want the Git sources stored inside the source package (temporary building is fine but not for long term persistent storage) and that the source packages are not self-modified like they would be if they were using the standard makepkg repository fetch and update methods. That means they'll never become standard AUR-ready source packages, as long as I'm building them, but that is not a great loss as they have proven to work quite well, as they are, for over 18 months now. The svn/ and the stephan/ trees could be merged and a new or modified build script could be put together that truly suits more than just my personal build server. The objective would be that anyone could simply run a script which pulls down the all the source packages, makes some simple mods like a change to Debug mode, and starts cloning or updating the users local git repo and builds and installs the whole set overnight... without having to mess around with any setup other than decide to commit to the download bandwidth, cpu time, storage required and running a single script.

So what does anyone think about this... time for a fresh cooperative start?

deej · 2009-08-18 10:20:12

Sounds like an excellent idea - if I knew my arse-from-my-elbow I'd happily
help out - time for some studying of the methods you will use.

Deej

markc · 2009-08-18 10:44:57

@deej: it is potentially not that hard once the system is set up right. All I do at night is type "mpkg-all" on my dedicated build machine (AMD 6000+ w/ 3Gb ram, nothing special) and go to bed. Managing the source packages was really easy at Google Code but I am sure it could be at Github or Gitorious once the system is streamlined and scripts set up to deal with them. The gain for the pain of any first time learning effort is that, in the case of Gitorious, any time spent learning a new thang can be amortized over the years dealing with Qt or KDE in general. For instance, learning to use the Gitorious wiki system is the same time spent learning how to use the Qt/KDE wiki system etc... or your own gitorious.org repo for whatever reason. As for Git itself, and ssh keys and such, yes it's a pain to deal with but it is becoming the defacto dVCS system so any time spent learning Git-lore will be useful over the years. This is Linus' famous google talk about Git -> http://video.google.com/videoplay?docid … 4603874737

deej · 2009-08-18 10:53:55

I shall look into it now

Deej

Spy · 2009-08-18 18:17:08

Assome.. Why Okular cannot open any pdf file ? Anyone simillar issue ?

deej · 2009-08-18 19:17:01

Spy wrote:

Assome.. Why Okular cannot open any pdf file ? Anyone simillar issue ?

Is poppler installed ? The only problem I had like this with Okular was solved by installing
poppler - and maybe poppler-qt... can't recall exactly.

Deej

Spy · 2009-08-18 19:33:13

Thank you very much. Now works great! I had to install poppler-qt.... This package should be add to deps of kde anyway...

deej · 2009-08-18 19:50:39

You're welcome

Deej

atomopawn · 2009-08-18 21:02:53

Using my newfound git powers, I've updated the kdegraphics PKGBUILD to depend on poppler-qt.

deej · 2009-08-18 21:04:58

:lol::lol:

I'm just reading up on git - after having sat thru' Linus' hour-long video.
Quite entertaining... I kinda like the guy.

Deej

markc · 2009-08-19 02:09:16

Next step is for anyone intertested to sign up to http://gitorious.org, if they already have not done so, and we need to decide on a name for both the project and the team.

Any suggestion for the name of the project... "archlinux-source-packages-for-kde-from-git" is obviously way too long but it needs to mean something like that but as short as possible... kde-git-srcpkgs perhaps?

@atomopawn: do you mean here, or somewhere else? -> http://github.com/markc/kde-svn/raw/mas … s/PKGBUILD

atomopawn · 2009-08-19 03:07:32

Okay. I signed up for a gitorious account as "robertm" (my kde svn commit nick). I like kde-git-srcpkgs. Although maybe kde-git-pkgbuilds might be more in the spirit of what we want to do?

@markc: Yes, there. I added "poppler-qt" right after "libspectre". Did it not make it into your branch?

markc · 2009-08-19 04:28:24

I just removed the VLC stuff from this pkgbuild and it showed as being modified here @ http://github.com/markc/kde-svn/raw/mas … t/PKGBUILD so all I can think of is that you may be commiting the change locally but not following that commit with a "git push".

Yes, "kde-git-pkgbuilds" is probably about as short as it can get and still have the right meaning.

atomopawn · 2009-08-19 04:32:55

I did "git push origin master" after I committed. I'll check my git remote settings and make sure they're okay.

atomopawn · 2009-08-19 04:42:13

Actually, are you sure my changes didn't go through? I simply commented out a few lines. It looks to me like you then committed a change which deleted those same lines (and a few others) after they'd been commented out.

deej · 2009-08-19 05:31:07

markc wrote:

Next step is for anyone intertested to sign up to http://gitorious.org, if they already have not done so, and we need to decide on a name for both the project and the team.

OK; signed up - as "phinger".

Deej a.k.a phinger

markc · 2009-08-19 05:44:09

Here we go -> http://gitorious.org/kde-git-pkgbuilds and http://gitorious.org/+kde-git-pkgbuilders

I also set up a team called "kde-git-pkgbuilders" which owns "kde-git-pkgbuilds". So far it's just myself and atomopawn in that team so just sign up to gitorious.org and indicate you'd like to join this team in this thread and what your Gitorious username is. Now I have to figure out how to push the github packages to gitorious but there is no hurry until, really, the KDE folks are actively using Git at gitorious (they may be but I'm not sure what the current state of the svn to git changeover is).

markc · 2009-08-19 05:53:43

@atomopawn: apologies, I was confused about the vlc changes to kdesupport and the extra dependency for kdegraphics. I think I also committed the cardinal sin of not doing a git pull before a commit and git push.

@deej: added to http://gitorious.org/+kde-git-pkgbuilders

atomopawn · 2009-08-19 06:06:12

@markc: No problem. Thanks for getting everything set up.

I've added my ssh key to gitorious. Let me know if there's anything else I need to do.

venky80 · 2009-08-19 06:53:02

i am using virtualbox for kde-svn but my fonts look really shitty what can I do?
here is how it looks like http://imagebin.ca/view/X7Dpvc.html

deej · 2009-08-19 06:53:36

ssh key also added.

Now I'll spend the day backing-up and preparing.

Anyone any thoughts on the mechanics of this regarding how it will work
on group members machines ? That is, do we freeze kde-svn at a certain
point; install it on a separate partition [ to dual boot with a std install of
Arch ] and then use that as our base Master ? Ideas ... ?

Deej the phinger

Last of the Wolves · 2009-08-19 08:46:49

I just signed in at gitorious. User lastofthewolves (what a suprise :-)).

I will set everything up on my new Server as soon as arch is set up there.

@deej: I'm using my standard productive system to compile at.

deej · 2009-08-19 09:11:06

= @deej: I'm using my standard productive system to compile at.

I was just wondering if it would be more rigorous to keep kde-git apart. This way
user-installed rubbish couldn't pollute the build. Once built, of course, there is
nothing to prevent anyone from installing the build on their 'normal' system to
test it thoroughly, with user-installed rubbish It may be just me being too clinical...
I'll give it a shot anyway; I've never tried booting two Arches before

Deej

Arch Linux

#1426 2009-08-18 06:03:14

Re: Daily KDE4 Subversion Packages

#1427 2009-08-18 07:03:54

Re: Daily KDE4 Subversion Packages

#1428 2009-08-18 10:01:37

Re: Daily KDE4 Subversion Packages

#1429 2009-08-18 10:20:12

Re: Daily KDE4 Subversion Packages

#1430 2009-08-18 10:44:57

Re: Daily KDE4 Subversion Packages

#1431 2009-08-18 10:53:55

Re: Daily KDE4 Subversion Packages

#1432 2009-08-18 18:17:08

Re: Daily KDE4 Subversion Packages

#1433 2009-08-18 19:17:01

Re: Daily KDE4 Subversion Packages

#1434 2009-08-18 19:33:13

Re: Daily KDE4 Subversion Packages

#1435 2009-08-18 19:50:39

Re: Daily KDE4 Subversion Packages

#1436 2009-08-18 21:02:53

Re: Daily KDE4 Subversion Packages

#1437 2009-08-18 21:04:58

Re: Daily KDE4 Subversion Packages

#1438 2009-08-19 02:09:16

Re: Daily KDE4 Subversion Packages

#1439 2009-08-19 03:07:32

Re: Daily KDE4 Subversion Packages

#1440 2009-08-19 04:28:24

Re: Daily KDE4 Subversion Packages

#1441 2009-08-19 04:32:55

Re: Daily KDE4 Subversion Packages

#1442 2009-08-19 04:42:13

Re: Daily KDE4 Subversion Packages

#1443 2009-08-19 05:31:07

Re: Daily KDE4 Subversion Packages

#1444 2009-08-19 05:44:09

Re: Daily KDE4 Subversion Packages

#1445 2009-08-19 05:53:43

Re: Daily KDE4 Subversion Packages

#1446 2009-08-19 06:06:12

Re: Daily KDE4 Subversion Packages

#1447 2009-08-19 06:53:02

Re: Daily KDE4 Subversion Packages

#1448 2009-08-19 06:53:36

Re: Daily KDE4 Subversion Packages

#1449 2009-08-19 08:46:49

Re: Daily KDE4 Subversion Packages

#1450 2009-08-19 09:11:06

Re: Daily KDE4 Subversion Packages

Board footer