[maemo-developers] Standardization of packages version name in the extra repositories

From: Murray Cumming murrayc at murrayc.com
Date: Fri Jul 25 15:28:10 EEST 2008
On Fri, 2008-07-25 at 13:21 +0100, Andrew Flegg wrote:
> On Fri, Jul 25, 2008 at 1:17 PM, Murray Cumming <murrayc at murrayc.com> wrote:
> > On Fri, 2008-07-25 at 11:20 +0100, Andrew Flegg wrote:
> >
> [snip]
> >> * Any package patched, or not from a existing deb source, needs to
> >> have a maemo version suffix.
> >
> > So every single package in extras should have a maemo suffix?
> 
> No, because some projects will be simple repackages of an upstream
> package with no additional Maemo patches which aren't available
> upstream.

Ah, thanks, that seems to be the opposite of what you say above.

So, how about packages that are not in debian? When you say "upstream"
here, it's not clear whether you mean upstream debian or upstream
source. upstream normally means source.

We should strongly discourage any patches that are not submitted to the
upstream (source) projects.

I suggest that these rules should be stated somewhere simply on a wiki
page, not somewhere deep in a PDF.

> For example, Maemo Mapper has no Maemo-specific patches and so the
> upstream version *is* the version of the deb. Similarly, something
> that's come from (say) mud from an upstream deb without any further
> patches (probably, typically, CLI apps) would also not have a maemo
> suffix.
> 
> However, if the upstream source can't build a Maemo package, or it's a
> package solely put together for Maemo, it needs a maemo suffix.
> 
> That's my understanding - hopefully Eero could correct me?
> 
> Cheers,
> 
> Andrew

-- 
murrayc at murrayc.com
www.murrayc.com
www.openismus.com


More information about the maemo-developers mailing list