[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Depending on another package's source



On Saturday 31 July 2004 15:45, Florian Weimer wrote:
> * Andrew Suffield:
> > On Sat, Jul 31, 2004 at 03:16:50PM -0600, Wesley J Landaker wrote:
> >> GHDL is a VHDL compiler that's implemented as a stand-alone
> >> language target for GCC. The way it's typically compiled is by:
> >>
> >> 1) Unpacking the latest GCC sources -- only gcc-core is necessary.
> >> 2) Unpacking GHDL on top (adds 'vhdl' directory, no other
> >> modifications) 3) Compile GCC with --enable-languages=vhdl
> >
> > This is a lunatic approach for an upstream to take. Granted that
> > branching gcc is excruciatingly difficult - but distributing
> > partial source really does suck.
>
> It's quite common in GCC-land, and I really don't see what's so wrong
> with it. 8-)

Well, it would be really cool if there was some better way to hook into 
GCC with new languages, but as you say, this seems to be the de-facto 
way to do it.

> >> For packaging this I thought of several different scenerios:
> >>
> >> A) Include the source of gcc-core in the .orig.tar.gz
> >>   Pro: it's the only way I've thought of yet
> >>   Pro: immunity to [hypothetical] changes in new versions GCC
> >>   Con: it duplicates some of what's in the gcc source package
> >
> > That's about the best you're going to get. You have to undo the
> > lunacy by fixing a specific version of the gcc source anyway.
>
> Yes, I agree that's the way to go.

Thanks. I appreciate the input, Florian.

-- 
Wesley J. Landaker <wjl@icecavern.net>
OpenPGP FP: 4135 2A3B 4726 ACC5 9094  0097 F0A9 8A4C 4CD6 E3D2

Attachment: pgpwhk5ouh57q.pgp
Description: signature


Reply to: