On Saturday 08 February 2014 09:01:46 Tzafrir Cohen wrote: > On Fri, Feb 07, 2014 at 10:41:56AM -0600, Michael Shuler wrote: > > On 02/07/2014 10:25 AM, Pau Garcia i Quiles wrote: > > >Is there a policy on how to package software that does not make releases? > > > > A version similar to skia_0.0-1~svnr1234 would allow an upstream > > version of i.e. 0.1 (if they ever release) to supersede your > > packaged version. It should also allow you to upgrade via new svn > > version (0.0-1~svnr1235), as well as new packaging of same svn > > version (0.0-2~svnr1234). Please, correct me, if there is a better > > method, here! > > One other thing to keep in mind: what if they switch to git? You could use a more generic prefix like vcs, I guess. Something like 0+vcs20140212-1 would use the snapshoot as "upstream", while allowing you to change the debian part, unlike a native package. Using the ~ non-trivial system is not needed, since any release version would be greater than "0" anyways. Still, ~ shows it's a pre-release, so it makes sense too. Just my noob 2 cents. ^^
Attachment:
signature.asc
Description: This is a digitally signed message part.