OpenConnect --version in patched package builds

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

 



On Fri, 2015-01-09 at 09:43 -0500, Mike Miller wrote:
> On Fri, Jan 09, 2015 at 10:03:00 +0000, David Woodhouse wrote:
> > Is there an equivalent for Debian packaging that I should check for too?
> 
> No, there is no standard set of environment variables passed to the
> build. We could agree on a convention and I could export a variable from
> the debian/rules script, but that's not much better than touching or
> modifying version.c myself.
> 
> I've been handling version.c to some extent for a while anyway, but I'll
> look at adding the Debian revision now to be equivalent to what you
> have.

Note that in the common (hopefully!) case of an *unpatched* OpenConnect,
I don't use the RPM package revision. It's just the normal contents of
version.c

The new RPM stuff only kicks in when the sources are patched (without
subsequently touching version.c) and we would *otherwise* have ended up
with "v7.03-unknown".

-- 
dwmw2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5745 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20150109/bcdf0ad7/attachment.bin>


[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux