[CCC DEV] Building for Debian/Ubuntu simplified

[cljacobsen at gmail.com]

I'm wondering. Is there any reason to install in /opt, other than
Matts fear of messing things up? (I think I remember that being the
reason).

The package manager should sort that out (ie avoiding our package
overwriting, deleting, etc, files that it shouldn't) and I'd rather
have the package install things in the usual places than in /opt...
Using a package lint tool should also provide confidence in the
package doing the right thing.

Christian

On 6 July 2010 14:20, Matt Jadud <jadudm at gmail.com> wrote:
> Hi all,
>
> If you check out
>
> svn co http://projects.cs.kent.ac.uk/projects/kroc/svn/kroc/branches/avr-mega/distribution/deb-pkg
>
> you'll get a small directory. (You could, I suppose, just download the
> Python script directly...)
>
> wget http://projects.cs.kent.ac.uk/projects/kroc/svn/kroc/branches/avr-mega/distribution/deb-pkg/make-deb-pkg.py
>
> In it is a Python script. You can invoke it thusly:
>
> python make-deb-pkg.py --all
> http://projects.cs.kent.ac.uk/projects/kroc/svn/kroc/trunk
>
> and it will checkout, configure, make, and create a Debian package of that URL.
>
> It is still not a "good" Debian package (meaning, it wouldn't be
> accepted into the mainline distribution channels), but the script will
> serve as a starting point for automating the process of generating
> good packages. In the meantime, this is a "binary" package that just
> installs the binaries and libraries that you need in
> /opt/occam/arduino.
>
> Hope that helps,
> Matt
>
> (This is useful for us hacking on libraries... instead of doing
> anything ugly when libraries refresh, we just refresh the package and
> remove/install. See the notes at the top of the script.)
>
> --
> Sent from my TRS-80
>
> _______________________________________________
> developers mailing list
> developers at concurrency.cc
> http://unhosting.org/mailman/listinfo/developers
>