3:37 a.m.
Hi Luc (and all crash developers on Cc),
since libeppic is now used at least by two projects (crash and
makedumpfile), I packaged it for openSUSE, but I cannot get it included
in Factory because of versioning policies for snapshot releases.
If I knew the planned target version, I could package the git snapshot
as a pre-release, but currently I can't, because I don't know if you
want to continue with the sial versioning scheme (last published was
sial-3.0), or start again from 1.0 (or even 0.1?).
Unless I'm missing something, I cannot see any public (versioned)
release of libeppic right now. Please, can you advise?
Thanks in advance,
Petr Tesarik
5:21 a.m.
Petr, lets give it a version of 2.0.
What is the easiest way to advertise that version from the source itself?
Eppic has been very stable and I do not expect to change that version any
time soon.
On Tuesday, April 2, 2013, Petr Tesarik wrote:
Hi Luc (and all crash developers on Cc),
since libeppic is now used at least by two projects (crash and
makedumpfile), I packaged it for openSUSE, but I cannot get it included
in Factory because of versioning policies for snapshot releases.
If I knew the planned target version, I could package the git snapshot
as a pre-release, but currently I can't, because I don't know if you
want to continue with the sial versioning scheme (last published was
sial-3.0), or start again from 1.0 (or even 0.1?).
Unless I'm missing something, I cannot see any public (versioned)
release of libeppic right now. Please, can you advise?
Thanks in advance,
Petr Tesarik
--
- Luc
5:59 a.m.
On Tue, 2 Apr 2013 06:21:34 -0400
Luc Chouinard <lucchouina(a)gmail.com> wrote:
Petr, lets give it a version of 2.0.
What is the easiest way to advertise that version from the source itself?
Eppic has been very stable and I do not expect to change that version any
time soon.
There is a preprocessor define in libeppic/eppic_api.h:
/* minor and major version number */
#define S_MAJOR 3
#define S_MINOR 0
I think that the S_ prefix stands for SIAL. ;-)
Plus, this definition is used by eppic_version in
applications/crash/eppic.c, and is advertised to users when you load
the eppic crash extension, so merely changing it to 2.0 would appear as
a downgrade...
I don't care too much how you implement it. Most libraries advertise
the version in a header file, so I would go for something like:
#define EPPIC_VER_MAJOR 2
#define EPPIC_VER_MINOR 0
If you're going to maintain stable library API, you may want to add a
third version digit for binary compatible additions:
#define EPPIC_VER_MICRO 0
Given the size of the project (and absence of a dynamic library, so
the runtime version must be equal to the compile-time version), the
last bit is probably pure overkill. In any case, I can add all this
later if I convert libeppic to a dynamic library.
Thanks,
Petr
On Tuesday, April 2, 2013, Petr Tesarik wrote:
> Hi Luc (and all crash developers on Cc),
>
> since libeppic is now used at least by two projects (crash and
> makedumpfile), I packaged it for openSUSE, but I cannot get it included
> in Factory because of versioning policies for snapshot releases.
>
> If I knew the planned target version, I could package the git snapshot
> as a pre-release, but currently I can't, because I don't know if you
> want to continue with the sial versioning scheme (last published was
> sial-3.0), or start again from 1.0 (or even 0.1?).
>
> Unless I'm missing something, I cannot see any public (versioned)
> release of libeppic right now. Please, can you advise?
>
> Thanks in advance,
> Petr Tesarik
>
4108
days inactive
4108
days old
devel@lists.crash-utility.osci.io
2 comments
2 participants
participants (2)
-
Luc Chouinard -
Petr Tesarik