[CCC DEV] Building for Debian/Ubuntu simplified

[cljacobsen at gmail.com]

I know the package won't get into the package repos, but i'm not sure
that is a good reason to put the stuff in opt. Also consider that
while it is easy to change the location of the package, once you have
users of your package then it becomes more complex (certainly from a
users perspective, ie: "OMG all concurrency.cc stuff used to be in
/opt, now it is all gone! WTS just happened"). I also prefer that the
package files live with everything else in /usr which is a known
"don't mess with" area, which "/opt" is not so much IMHO. So with
things living in /usr you might get fewer ppl poking at stuff
resulting in breakage and unnecessary mailing list traffic :)

But props on the automation bit, this is just my opinion on /usr vs /opt

Cheers,
  Christian


On 6 July 2010 14:45, Matt Jadud <jadudm at gmail.com> wrote:
> 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
>