[seedkit-list] Build SeedKit in a sane way?

[Joern Konopka <cldx3000 googlemail com>]

Hi everybody, since its my first post around here let me introduce myself real quick, my name is Joern Konopka and i'm into pretty much anything that revolves around Gnome and my Distribution of Choice (which would be Ubuntu, please don't beat me ;). I have some advanced knowledge with Web Technology as well as Traditional/Digital Drawing and Illustration Media and some noobish basic knowledge about the Gnome Ecosystem, we all had to start somewhere right?

So why am i writing this?

Im having some heavy troubles getting SeedKit to properly build on my Machine, or to be more precise, i barely know where to get the proper resources! Im not really good with all the Packaging Stuff, so to give you an example, if you say i have to install webkit-3.0 i'll be baffled to find out that the actual package name is probably more along the lines of libwebkit-2.9.7 or something like this. Not even talking about packages that are not to be found in any official repositories but f.e. on gitorious or github.

So what do you want?

Obviously one of the main targets for SeedKit is to reach out to a wider field of Devs, especially including Web Developers and their Knowledge Base which has been artificially separated from other Programming and Descriptive Languages for reasons beyond my understanding since we probably all agree on the idea that the Web of today will be the Desktop of tomorrow. So what we really need right now is a real Hands-On Tutorial for the non-sudomakeinstall population of the Gnomesphere. Questions arise as stated below:

-Exactly WHAT Packages do i have to install?

-Where can i find the source/deb/rpm for those packages?

-What kinda troubles might i be running into while building a sane SeedKit Environment?

-Does using all these bleeding-edge packages endanger my working environment (f.e. GTK-3.0)? You know, if you mess up a JS File, worst thing, your Browser crashes, but we are talking Desktop here, not Website, people dont wanna frag their Desktop just to try something cool.

- If there is a certain risk to the packages, how could we provide a way to work around that?

-So how did YOU get it to run on [Distro of your Choice]?

Now why don't you find out for yourself sucker?

Please don't dismiss this message behind under the assumption that i'm too stupid to compile from source or find some packages, the main goal of this Mail is to aggregate user experiences during building the environment, Best Practice on how to proceed to a fully working SeedKit Environment across many different Distributions as well as making it easy as pie for hopefully many, many future Developers to get SeedKit up and running even though they barely have a clue of how Software actually compiles (you know, you don't compile too much writing HTML and CSS usually ;).

As soon as we gathered some insight that will be usable for the common "Newbie" we can approach writing out some Tutorials and resource collections that might as well include resources for learning stuff like GIO and provide a Showcase for SeedKit Examples and Tutorials that everybody can take advantage of and point to for Beginners to read (of course a good starting point would be the Gnome Live Page ;). 

Tomorrow i will follow up this email with my current experiences with SeedKit, right now im just too tired (sorry Alexandre, im still high on Meds ;), so keep it coming, seeing there aren't too many people around here is obviously a sign of a massive accessibility barrier for WebDevs-going-Desktop and less one of lack of interested people. 

Until tomorrow (when i will annoy you with more of my world-domination fantasies) i hope all of you enjoyed your weekend and will have a great start into the new week to come.

--
Why don't you start at the beginning? Yes, and when you reach the end... Stop.
twitter.com/cldx3000