[CCC DEV] Building for Debian/Ubuntu simplified

[Matt Jadud]

On Tue, Jul 6, 2010 at 8:35 AM, cljacobsen at gmail.com
<cljacobsen at gmail.com> wrote:
> 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.

As written, it only requires changing one variable to change the
target destination. (Well, that's not true... we'll have to change a
few variables, to put sensible things in sensible places.) However,
moving to a "normal" Debian install won't be a difficult task.

Mostly, I was under the impression from my initial reading that the
package I'm building won't pass muster for inclusion in the mainline
repositories (for a variety of reasons). For that reason, I'm not
worried about it being in /opt *just yet*. Moving the installation
target elsewhere will be an easy thing... making sure it passes
"lintian," etc., will take more effort.

The automation of these steps makes things easier for the students who
are helping out this summer, if nothing else. Whether it hangs around
for the long term... well, that doesn't really matter. It does clean
up the previous script, and solves a real problem, all for a minimum
of time spent.

Cheers,
M