On Wed, Aug 1, 2012 at 4:13 PM, Paul Moore <pmo...@redhat.com> wrote:
> On Wednesday, August 01, 2012 09:54:25 AM Eduardo Otubo wrote:
> > Just a typo for the new release.
> > I don't tihnk it deserves a patch anyway, but just saying :)
>
> Thanks, for checking on this, but I changed the version number in the
> release-1.0.0 branch. I plan to keep the master branch always at 0.0.0 so
> it
> will always be obvious if someone is running a "development" version of the
> library.
>
> > Signed-off-by: Eduardo Otubo <ot...@linux.vnet.ibm.com>
> > ---
> > version_info | 2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/version_info b/version_info
> > index 7520e4f..c88de08 100644
> > --- a/version_info
> > +++ b/version_info
> > @@ -3,6 +3,6 @@
> > #
> >
> > # version components
> > -VERSION_MAJOR=0
> > +VERSION_MAJOR=1
> > VERSION_MINOR=0
> > VERSION_MICRO=0
>
Would be nice if we could keep the master version the same as the latest
release. This is what is happening to me, I'm wondering if others have the
same issue.
My CMake buildsystem has the snippet bellow:
INCLUDE(FindPkgConfig)
PKG_CHECK_MODULES(LIBSECCOMP REQUIRED libseccomp>=1.0.0)
I gonna have to patch libseccomp to try the development version, otherwise
pkgconfig will complain. The situation gets worse if right after a release
you find a security hole and have to patch both the release branch and the
master. I suggest the kernel way of making releases by creating a tag at
the commit on the master that changes the version number.
Cheers,
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
libseccomp-discuss mailing list
libseccomp-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libseccomp-discuss
