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

Re: RFC: Exploded source repo layouts

On Wed, 2008-07-23 at 16:55 +0200, Dominik 'Rathann' Mierzejewski wrote:
> On Wednesday, 23 July 2008 at 10:16, Andreas Ericsson wrote:
> > Hans de Goede wrote:
> > >Doug Ledford wrote:
> > >>I've been working on getting this set up and functional.
> > >
> > ><lots of complicated hacks and workarounds deleted>
> [...]
> > >It seems there are a few people who are a big fan of this, and about as 
> > >much active opponents. I have no problems with adding the possibility to 
> > >use a distributed VCS with exploded trees to the mix of ways to maintain 
> > >and build packages, but this should not replace the current nice and 
> > >simple setup we have.
> > >
> > 
> > Noone has proposed replacing the existing setup, so the rest of your
> > email can safely be delegated to /dev/null.
> Let me provide the missing quote then:
> > >>First, we have to do away with a bunch of our make targets because they
> > >>are too commonly named and might conflict with legitimate upstream make
> > >>targets (well, more like some of them might conflict, some of them
> > >>*definitely* conflict).  This is important because our Makefile.common
> > >>is included in upstream's toplevel Makefile.
> If that doesn't touch our existing setup then fine, but I'm afraid
> Doug really meant what he wrote.

Actually, no.  For Makefile.dist-CVS, it is the same as it used to be.
Same make targets, same functionality, same, same, same.  It's
Makefile.repo-git that gets included in the exploded source's top level
Makefile, and *that's* where you have new make targets and such.

Doug Ledford <dledford redhat com>
              GPG KeyID: CFBFF194

Infiniband specific RPMs available at

Attachment: signature.asc
Description: This is a digitally signed message part

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