On Sat, 2009-10-03 at 10:12 +0200, Jonas Smedegaard wrote: > On Fri, Oct 02, 2009 at 04:21:00PM -0400, Felipe Sateler wrote: > >On Fri, 2009-10-02 at 13:51 +0200, Jonas Smedegaard wrote: > >> On Thu, Oct 01, 2009 at 01:56:07PM -0400, Felipe Sateler wrote: > >> >I'm not sure if this should be a new bug, but this one is close > >> >enough. > >> > > >> >cdbs (debhelper.mk) provides install/binarypackage targets for each > >> >binary package. However, it does not provide the install target > >> >which sometimes is very useful. Adding it should be a matter of > >> >adding: > >> > > >> >install:: $(patsubst %,install/%,$(DEB_ALL_PACKAGES)) > >> > > >> > > >> >Somewhere in debhelper.mk > >> > >> Providing a new make target has a risk of clashing with existing > >> target of same name but of different type - i.e. above will break > >> packages currently crestihng an install: target (using single colon). > > > >Hmm. A different name is an option. The important thing is to have a > >convenient way to perform the install stage, but not create the binary > >debs. cdbs-install > > Ahh, so it is not because you want some rules attached to that target, > just that you want a single target that all install targets depend on?
Neither. I want to populate debian/tmp/*. Any multi-binary package may have several install/package:: rules, and I want a way to conveniently perform all of them. > > I think that is a good idea idea for cdbs v2 but I do not imagine an > elegant way to add it to current cdbs structure without risk of causing > surprises. I think common-install-impl does what you are explaining. I want some sort of post-install target, not necessarily to add rules (since install/package is usually sufficient for that), but to populate debian/tmp/* and see if my rules and *.install files are working correctly. -- Saludos, Felipe Sateler
signature.asc
Description: This is a digitally signed message part
