Merge lp:~tom-gall/linaro-seeds/linaro.natty-add-linaro-development into lp:linaro-seeds/natty

[Tom Gall]

- remove linaro-core-dev
- add linaro-development which stacks on top of linaro-headless

resubmit based on feedback from earlier today (thanks)

debian tools is now just build-essentials and diff

included tools are devmem2, gdb, gdbserver, iotop, input-utils, i2c-tools, lsof, ltrace, oprofile, powertop, strace, systemtap and usbutils as identified at UDS-N

Other packages thrown in for usefulness include vim, and openssh-server

[Steve Langasek (vorlon)]

+= debian tools =
+ * build-essential
+ * devscripts
+ * ubuntu-dev-tools
+ * debhelper
+ * dh-make
+ * diff
+ * patch
+ * cdbs
+ * quilt
+ * gnupg
+ * fakeroot
+ * lintian
+ * pbuilder
+ * piuparts

With the possible exception of build-essential, these don't belong in the developer image. The purpose of the developer image is to facilitate debugging, compiling, and profiling, not package building and QA work. These also weren't discussed at all in the UDS "developer image" session.

If there is a need for a "package development" seed, it needs to be a separate seed. Also, I don't think packages such as debhelper or cdbs (especially cdbs!) belong in it; these are build-dependencies, not part of a generic developer toolkit, and shouldn't be treated differently than any other build dependencies (i.e., they'll be installed when you need them).

+ * evtest

I think the conclusion in the session was that input-utils does this job for us already.

+ * i2c-utils

Package name is i2c-tools

+ * system-tap

Package name is systemtap

+ * usb-utils

Package name is usbutils

+= scm =
+ * bzr
+ * bzrtools
+ * git

This was also not in the session notes - in fact, I recall people saying they are almost certainly not going to care about git on the image because they're going to do their development on a separate build machine. Where does the requirement for this come from?

review: Needs Fixing

[James Westby (james-w)]

On Wed, 17 Nov 2010 21:47:52 -0000, Steve Langasek <email address hidden> wrote:
> With the possible exception of build-essential, these don't belong in
> the developer image. The purpose of the developer image is to
> facilitate debugging, compiling, and profiling, not package building
> and QA work. These also weren't discussed at all in the UDS
> "developer image" session.

Agreed, but I think diff and patch might be desirable. They probably
have the same arguments as the VCS tools, so you might want to keep them
out if you keep them out.

Thanks,

James

[Tom Gall (tom-gall)]

It's interesting that germinate, live-helper and friends didn't spit out errors at some point in the usual image building cycle. <shrug>.

I can appreciate that for some developers where the output of their work is patches won't care one bit about creating debs. However that is not necessarily the case for all developers. In some contexts creating packages is a development activity, ergo the presence of packaging tools in this suggested seed. I'd kinda like to avoid something like linaro-package-developer stacking on top of something like this.

As far as scm goes, I do remember those comments by some. Is it a requirement that these tools be here? I'm not sure that that is the case, but I'm not convinced it's not the case. Speaking for myself, having them there preinstalled would be useful but I am but one dev who performed two installs today and these were part of what I had to install.

[Steve Langasek (vorlon)]

On Wed, Nov 17, 2010 at 09:59:25PM -0000, James Westby wrote:
> On Wed, 17 Nov 2010 21:47:52 -0000, Steve Langasek <email address hidden> wrote:
> > With the possible exception of build-essential, these don't belong in
> > the developer image. The purpose of the developer image is to
> > facilitate debugging, compiling, and profiling, not package building
> > and QA work. These also weren't discussed at all in the UDS
> > "developer image" session.

> Agreed, but I think diff and patch might be desirable. They probably
> have the same arguments as the VCS tools, so you might want to keep them
> out if you keep them out.

'patch' is pulled in for us by build-essential; diff is not, I thought it
was. So ok, maybe build-essential + diff.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[lp:~tom-gall/linaro-seeds/linaro.natty-add-linaro-development]

45. By Tom Gall on 2010-11-22

 add a linaro-development seed which includes tools for building, debugging, profiling, tracing on and so on that is of use to developers

Unmerged revisions

=== modified file 'STRUCTURE'
--- STRUCTURE	2010-08-29 16:51:38 +0000
+++ STRUCTURE	2010-11-22 21:55:13 +0000
@@ -1,6 +1,6 @@
 include platform.maverick
 linaro-headless: minimal
-linaro-core-dev: linaro-headless
+linaro-development: linaro-headless
 linaro-x11-base: linaro-headless
 linaro-netbook-efl: linaro-x11-base
 linaro-xfce-base: linaro-x11-base

=== removed file 'linaro-core-dev'
--- linaro-core-dev	2010-09-08 10:39:29 +0000
+++ linaro-core-dev	1970-01-01 00:00:00 +0000
@@ -1,34 +0,0 @@
-Task-Per-Derivative: 1
-Task-Section: user
-Task-Description: Linaro Core Development Packages
-Task-Extended-Description: This task provides the Linaro Core Development Packages
-Task-Metapackage: linaro-core-dev
-Task-Key: linaro-core-dev
-Task-Name: linaro-core-dev
-Task-Seeds: minimal linaro-headless
-
-= Toolchain =
-
- * build-essential
-
-= Kernel Headers =
-
-Provide here the header for each kernel version.
-The issue is when we try to build kernel drivers, it does install the wrong
-version depending on what kernel you start with, but it's not resolvable until
-sticky dependencies are introduced in apt. (see bug #318727)
-
- * (linux-headers-generic) [i386]
- * (linux-headers-powerpc) [powerpc]
- * (linux-headers-powerpc64-smp) [powerpc]
- * (linux-headers-generic) [amd64]
- * (linux-headers-ia64) [ia64]
- * (linux-headers-sparc64) [sparc]
- * (linux-headers-hppa32) [hppa]
- * (linux-headers-hppa64) [hppa]
- * (linux-headers-lpia) [lpia]
- * (linux-headers-imx51) [armel]
- * (linux-headers-dove) [armel]
- * (linux-headers-omap) [armel]
-
-

=== added file 'linaro-development'
--- linaro-development	1970-01-01 00:00:00 +0000
+++ linaro-development	2010-11-22 21:55:13 +0000
@@ -0,0 +1,36 @@
+Task-Per-Derivative: 1
+Task-Section: user
+Task-Description: Linaro Development Packages
+Task-Extended-Description: This task installs commen packages software developers will want 
+Task-Key: linaro-development
+Task-Name: linaro-development
+Task-Metapackage: linaro-development
+Task-Seeds: minimal linaro-headless 
+
+= infrastructure =
+
+ * openssh-server
+
+= debian tools =
+ * build-essential 
+ * diff 
+
+= debug / profile / trace etc tools =
+
+ * devmem2
+ * gdb
+ * gdbserver
+ * iotop
+ * input-utils
+ * i2c-tools
+ * lsof
+ * ltrace
+ * oprofile
+ * powertop
+ * strace
+ * systemtap
+ * usbutils
+
+= editors =
+ * vim
+