elementary-dev-community team mailing list archive

["Sergey \"Shnatsel\" Davidoff" <sergey@xxxxxxxxxxxxxxxx>]

> Now I am fully aware that maybe this would be a hard work, and
> possiblylimiting to the fact that having everything shipped, would mean
> largeriso imageswhich then could be "bad" in terms of upload + updated
> state of the iso.So another idea to support this view would go towards a
> "ElementaryDeveloper MetaPackage" that would take care of preparing a nice
> development environment.
>

Yep, it's on the radar, see
https://blueprints.launchpad.net/elementaryos/+spec/dev-metapackage-elementary(and
http://elementaryos.org/journal/how-see-what%E2%80%99s-our-sleeves on using
blueprints, if you're not familiar with them).

But first we need an SDK to put into the metapackage, which we currently
don't have (in a complete or stable state at least). There's
GrabIt<https://code.launchpad.net/~elementary-os/elementaryos/grabit>but
it's not that great for novice devs anyway and Tom has a project
creation script, both of which should probably become a part of Euclide,
our work-in-progress IDE at some point...

Right now we're too busy with getting Luna out of the door, but I'd expect
toolset and SDK work to happen right after Luna release.

If you want the libraries needed for developing our software, just use
> "sudo apt-get source", *any* developer should know how to get this kind
> of tools. Using bazaar to branch and build our tools from source is also
> something our developers *must* know how to do.
>

apt-get source and bzr are by far not the most developer-friendly things.
In fact, apt-get source has absolutely nothing to do with developers at
all, and the fact that some people consider it so only proves that our
toolset is confusing.

Not to mention that we don't even have an into into all these things, yet.

-- 
Sergey "Shnatsel" Davidoff
OS architect @ elementary