(Somehow I think we should move this sub-discussion somewhere else, ccing
debian-dpkg for a start, feel free to drop the bug when replying.
It would also be nice to have the feedback of others on this idea.)
On Mon, 20 Jun 2011, Modestas Vainius wrote:
> I disagree that this is a trend set by debh
Hello,
On pirmadienis 20 Birželis 2011 15:01:58 Raphael Hertzog wrote:
> > Anyway, then my patch is not really helping. Dh_Lib.pm part should be
> > reverted and documentation should be fixed once we decide on the
> > recommended practises. Having in mind #613046 , what's the recommended
> > way t
On Mon, 20 Jun 2011, Modestas Vainius wrote:
> > Hum, DEB_*_APPEND/SET were meant for users recompiling packages not really
> > for package maintainers. The logic was that dpkg-buildflags gives a set
> > of base flags and that the package can then tweak them.
>
> Those intentions are not clear fro
Hello,
On pirmadienis 20 Birželis 2011 09:08:53 Raphael Hertzog wrote:
> Hi,
>
> On Mon, 20 Jun 2011, Modestas Vainius wrote:
> > On the other hand, it is really too bad that 'export
> > DEB_LDFLAGS_{APPEND,SET} = ' will have no effect as long as
> > dpkg-buildpackage keeps modifying environment.
Hi,
On Mon, 20 Jun 2011, Modestas Vainius wrote:
> On the other hand, it is really too bad that 'export DEB_LDFLAGS_{APPEND,SET}
> = ' will have no effect as long as dpkg-buildpackage keeps modifying
> environment. Both LDFLAGS and DEB_LDFLAGS_APPEND would need to be exported
> (or
> LDFLAGS u
Hello,
On sekmadienis 19 Birželis 2011 21:20:37 Joey Hess wrote:
> Modestas Vainius wrote:
> > The upside of this aggressiveness is that sensitive environment
> > variables, that might already have been set before debian/rules, will be
> > overwritten and won't affect build of the package. I do un
Hi,
On Sun, 19 Jun 2011, Joey Hess wrote:
> > I don't understand why you do not use Dpkg::BuildFlags directly. Its API is
> > marked as stable (our $VERSION = "1.00" [2]). I'm CC'ing Raphael in case
> > I'm
> > suggesting something wrong.
>
> Thanks, much better.
Yes, it's ok to use Dpkg::Bui
Modestas Vainius wrote:
> Hello,
>
> On šeštadienis 18 Birželis 2011 23:39:50 Modestas Vainius wrote:
> >
> > The upside of this aggressiveness is that sensitive environment variables,
> > that might already have been set before debian/rules, will be overwritten
> > and won't affect build of the
Modestas Vainius wrote:
> The upside of this aggressiveness is that sensitive environment variables,
> that might already have been set before debian/rules, will be overwritten and
> won't affect build of the package. I do understand that doing the same would
> break backwards compatibility in d
Hello,
On šeštadienis 18 Birželis 2011 23:39:50 Modestas Vainius wrote:
>
> The upside of this aggressiveness is that sensitive environment variables,
> that might already have been set before debian/rules, will be overwritten
> and won't affect build of the package. I do understand that doing th
Hello,
On trečiadienis 15 Birželis 2011 00:02:18 Joey Hess wrote:
> So, my only interest now WRT this bug is to support dpkg-buildflags in
> dh and dh_auto_* in a generic manner, and to support
> DEB_BUILD_OPTIONS=noopt as best possible.
>
> Since dpkg-buildflags could be used to set *any* variab
What a flaming mess. I will never, ever, again let debhelper be the
workaround point for a bad decision, such as the one made by the dpkg
maintainers with forcing CFLAGS. Not without being paid at twice
my standard consulting rate at least. You have been warned.
So, my only interest now WRT this
12 matches
Mail list logo
