On Tue 09 Apr 2013 13:43:02 Gergely Nagy escribió:
> Lisandro Damián Nicanor Pérez Meyer <lisan...@debian.org> writes:
> > On Sat 16 Mar 2013 18:47:51 Lisandro Damián Nicanor Pérez Meyer escribió:
> > [snip]
> >
> >> Also, as another way to achieve this, is adding the option to use
> >> foo.install.common
> >>
> >> So if you have foo.install.ARCH and foo.install.common, both files would
> >> be processed. This will not break previous behaviour.
> >
> > And another option will be simply allowing dh_install to accept a certain
> > file:
> >
> > dh_install --list-file foo.install.common
>
> You can also use dh9+ and executable install files, then assemble the
> files in whatever way you want. To make it easier, I'd be happy to add
> support for this kind of thing in dh-exec, so all you would need to do
> would be:
>
> * Add dh-exec to build-depends
> * cat >foo.install <<EOF
> #!/usr/bin/dh-exec
> #include foo.install.${DEB_HOST_ARCH}
> blah
> blah
> blah
> EOF
> * chmod +x foo.install
>
> Let me know if you're interested in using dh-exec for this task, and
> I'll add the necessary code there.Well, we eneded up using .install-$arch, .install-$os and .install-common, merge them in a single .install and then call dh_install, so I guess the solution is quite simple. It's currently in qtbase (qt 5 base), in NEW. Thanks a lot for offering help non the less :-) Kinds regards, Lisandro. -- Sólo porque un mensaje pueda no ser recibido no implica que no valga la pena enviarlo. Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
