Re: Packaging a difficult project

2007-08-04 Thread Brendon Costa
Steve Langasek wrote: >> I am not sure where the 1G comes from, unless talking about the >> duplicity across various mirrors. > > No, this is an estimate based on the actual usage of pool/main/g/gcc-4.1 on > current Debian mirrors. (12 archs * 3 versions * n binary packages) > > Your note on the

Re: Packaging a difficult project

2007-08-04 Thread Brendon Costa
Thomas Jollans wrote: > On Saturday 04 August 2007, Brendon Costa wrote: >> EDoc++ binaries are currently around 20M. It does not require any >> special binutils etc, but will just use what is already available for >> the system. I am currently building a single non-p

Re: Packaging a difficult project

2007-08-03 Thread Brendon Costa
> >> I believe that edoc doesn't use the code generator, only the front >> end, so it doesn't need care from port maintainers. > The GCC modification attempts to change as little in the GCC framework as possible and just performs analysis on the data structures generated by GCC as it compiles co

Re: Packaging a difficult project

2007-08-03 Thread Brendon Costa
Thanks for the response. > > Hmm, I would question whether this is something we'd want to include in the > Debian archive as-is; I think we already have way too many gcc packages > being carried around with our releases and that we need to try to make this > number go down, not add more copies of

Packaging a difficult project

2007-08-02 Thread Brendon Costa
Hi all, I was directed here from debian-mentors with my question. --- Original Post --- I have a software project that I plan on creating Debian packages for which is quite different from many other packages in that it also installs patched versions of GCC and Doxygen (That must not conflict