Emacs packaging

What’s the usecase?

@Licaon_Kter

  • if you replied to my post
  • i adherently follow concept known
    as “future-proof”, [ q ] dont know
    if its applicable for packages!

[ q ] Future-proof - Wikipedia


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

regards,
జిందం వాఐి [ jindam, vani ]

web_ jivani.neocities.org
[matrix]_ @jindam:catgirl.cloud

What’s the future you anticipate as requiring downgrades?

@repetitivestrain

i am asking again!

I’ve introduced a regularly updated version code into java/AndroidManifest.xml.in. It is altered whenever the repository’s version number is refreshed, including for pretests and prereleases, and as such I recommend against updating to revisions where the third pair of digits is not zero.

Where is it? Is it this one? AndroidManifest.xml.in\java - emacs.git - Emacs source repository

We can filter the tags with a regex.

It’s here: AndroidManifest.xml.in\java - emacs.git - Emacs source repository.

Are there any tags that should be skipped?

Any tag with three components in its version name (e.g. 30.1.60, 31.0.60, as against 30.1, 30.2, 31.1, etc).

Thank you!

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.