distribution and packaging

[Pierre Phaneuf]

On Sun, Mar 1, 2009 at 8:13 PM, Tom Tromey <tro...@peakpeak.com> wrote:

> Pierre> It seems also that the size footprint of Quagmire could be improved by
> Pierre> having fewer files: du tells me around 316K, tarred it makes for 200K,
> Pierre> gzipping down to 41K, but catting all the files together gives 59K,
> Pierre> gzipping down to 18K.
>
> Yeah, we could do that.  I just don't want to struggle too much to
> understand things; GNU make code is pretty hard to read as it is.
> But, there are various ways we can deal with that, like comments and
> page breaks.

That ties into distribution, in that we might want to pick and choose
some parts. I'd find it kind of silly of shipping out something like
Fortran support bits with Quadra, for example, or code for tests I do
not use (more realistically!). And you're quite correct that for
maintainability, you don't want to just dump the whole thing in a
single file (even though that )...

Maybe some form of "compiler" to glue the parts together? We could
write it in Perl, and have this caching mechanism, and... ;-)

> I set you up.  A few requests: please try to follow the coding style
> (which isn't hard since there isn't much to it :-), write ChangeLog
> entries, and keep everybody informed about changes you make.

Thanks! Where can I find the coding style guide? I presume that for
ChangeLog entries, this is the style from the GNU coding standards?

--
http://pphaneuf.livejournal.com/

[Tom Tromey]

>>>>> "Pierre" == Pierre Phaneuf <ppha...@gmail.com> writes:

Pierre> That ties into distribution, in that we might want to pick and
Pierre> choose some parts. I'd find it kind of silly of shipping out
Pierre> something like Fortran support bits with Quadra, for example,
Pierre> or code for tests I do not use (more realistically!).

Yeah, that would be nice.

Also I wondered if might tie into extensibility somehow -- I'd like to
provide a way for users to extend the list of supported languages (in
a way better than what automake provides) and I was occasionally
thinking this could be done by including files at runtime. Maybe not
though :)

Pierre> Maybe some form of "compiler" to glue the parts together? We could
Pierre> write it in Perl, and have this caching mechanism, and... ;-)

:)

Pierre> Thanks! Where can I find the coding style guide? I presume that for
Pierre> ChangeLog entries, this is the style from the GNU coding standards?

For ChangeLog, yeah. I don't think I wrote down any quagmire
guidelines. Stuff I remember:

* Try to give things names that won't conflict with user code. I
think this just means use "quagmire" as a prefix a lot.

* If you add something new, make sure to follow the existing
"cross-cutting" features. This means stuff like, respect DESTDIR
for new install targets, use quagmire/echo-n to print commands (and
configure output),

* For user-visible features, make it feel similar to existing quagmire
and/or automake usage.

Not much to worry about really :)

Tom