rules: improve handling of AUTORELEASE

[aparcar]

No longer depend on specific commit subjects (containing "update to" or
"bump to") but instead look for changes of PKG_VERSION or
PKG_SOURCE_DATE.

Signed-off-by: Paul Spooren mail@aparcar.org

[aparcar]

Thanks to @jow- for the single line solution. You should try CodeGolf

[aparcar]

@rsalvaterra @neheb cpuld you please give this a spin?

[xabolcs]

Thanks to jow- for the single line solution.

Suggested-by:? 😉

[rsalvaterra]

Looks much saner, indeed. Will test.

[jefferyto]

A few thoughts:

• Perhaps it would be better to track PKG_SOURCE_VERSION instead of PKG_SOURCE_DATE, since PKG_SOURCE_DATE is not strictly required when using PKG_SOURCE_VERSION
• If PKG_VERSION was moved but not changed, this would still be detected as a version change?
• If a package version was defined with something like:

  MAJOR_VERSION:=1
  MINOR_VERSION:=0
  PKG_VERSION:=$(MAJOR_VERSION).$(MINOR_VERSION)
  

  then this would not detect any version changes?
• Perhaps it would be better to include detecting changes to PKG_VERSION, etc. in addition to, instead of as a replacement for, detecting key phrases in the commit title (if this is possible)

[Ansuel]

@aparcar news on this?

@jefferyto in theory the PKG_RELEASE is used to detect changes on the package with the same version, am i wrong or changing PKG_VERSION would result in rebuilding the package and pushing a new version? (aka different PKG_VERSION with same PKG_RELEASE = new package anyway)

[Ansuel]

Closing this as AUTORELEASE is flagged as deprecated and should be dropped. Sad since it was a handy thing.