(fix typos) Re: Packaging:NamingGuidelines Re: DNF is completly unable to act with local packages

[Sérgio Basto]

On Ter, 2015-11-24 at 08:18 -0500, Jared K. Smith wrote:
> 
> On Mon, Nov 23, 2015 at 8:47 PM, Sérgio Basto <sergio at serjux.com>
> wrote:
> > we have two counters, one when upstream change the source
> > other when we rebuild the package, it will be better readable, to
> > understand if the upstream had updates or not.
> > 
> 
> Maybe I'm not understanding you well, but we *do* have two
> counters... in fact, we have *three*.  We have epoch, version, and
> release.  When an upstream community puts out a newer version of the
> software, the version number should increase.  When the packager puts
> out a new package with the same version number, she/he should
> increase the release number.  This is why pre-release software should
> have a release number that begins with "0.", so that when the
> production release happens, the release number can start at "1". 
> Last but not least, Epoch can be used to override the version and
> release numbers in special cases where the version and release
> numbers of a newer release don't sort to the top.  (One such example
> might be if we needed to downgrade a particular package for some
> reason.)
> 
> Does that help make things more clear?

Use epoch is one solution but in my mind, epoch is for breakage, we
should avoid use epoch, epoch was needed to install kde4 over F23 :) 
Thanks,
-- 
Sérgio M. B.