[Pkg-voip-commits] r7144 - /opal/trunk/debian/rules

[Eugen Dedu]

Kilian Krause wrote:
> Hi Eugen,
> 
>> 1. I still do not understand why you prefer ~.  +dfsg has no drawback. 
>> ~dfsg has: I need in ekiga to put depends opal 3.6.1~, which is awkward!
> 
> this has not been an issue in the past and it has even been necessary to
> put it for ~pre or ~rc versions (or the svn snapshots for that sake). Thus
> I'm not fully agreed that this is actually being wrong/worse (as opposed to
> possibly "feeling" wrong for you which I fully accept). I'm not sure how you
> did continue my snapshots in snapshots.ekiga.net but you may need to put it
> anyway there to ensure that the old scripts keep working ok (and actually
> produce usable debs). Moreover I'm not sure if there's any Ubuntu versions
> involved that may require this anyway too.
> 
> Anyway, if there is a fresh sourceful upload (i.e. new upstream release)
> of any of the packages this can be changed if you see there's a benefit but
> I definitely oppose doing a fresh sourceful upload just for the sake of it.
> 
> And as a sidenote, what are you going to do if some upstream would consider
> doing a 3.6.1+anypatch release himself? That would actually screw your point
> in + being superior to ~ as it *does* limit your options. The fact that only
> very few upstreams ever come to the point of factually rolling out such
> release is neither a guarantee nor a sustainable rationale for the solution
> of using +dfsg.
> 
> 
>> 2. This comes from the fact that ~ means before (sorts before nothing), 
>> while + means after (sorts after nothing).  So +dfsg seems to me the 
>> right one (I download, *after* that I remove iLBC).
> 
> There is always the way to also see it as reverting to the release state
> *before* this was added to the release tarball. Both don't have any greater
> relevance over the other unless you actually put a patch in that was not
> available before the release. Still from the point that you shouldn't be
> taking any options off the table with regard to what upstream may doing
> using ~dfsg has the greater robustness.
> 
> 
>> 3. The fact that lintian proposes this is a reason to think that the + 
>> is the right character.  lintian serves as a guide for all of us.
> 
> As said, if there is a clean upgrade with fresh upstream release I'm not
> generally standing in your way - just for me it feels not as clean and
> robust (wrt to I've seen all sorts of issues with naming issues from
> upstreams of pkg-voip packages). So whenever I can retain flexbility I'll
> rather go for that.
> 
> 
>> As for svn, I have not yet thought.  Anyway, it's not about svn here.
> 
> What I've explained was always my design when I was doing the
> "autobackports" and other svn snapshots in Buildserver.NET for Ekiga. So
> forgive me if my considerations are somewhat beyond the scope of what
> lintian tries to cover (for "just" Debian).

Hi Kilian,

Personally, I still think the + is a better choice.

But this is a really minor point, so let's stay with ~, as you prefer.

Cheers,
Eugen