Re: git revision number for package update

Hello Derek,

Thank you very much for your clarification. ( I was thinking about adding a “mv” command to the CompileScript.)

Greetings,
Ebrahim

> On Apr 22, 2020, at 2:51 PM, Derek Homeier <[email protected]> wrote:
> 
> On 22 Apr 2020, at 8:38 pm, Hanspeter Niederstrasser <[email protected]> wrote:
>> 
>>> 1. How can I get the revision number of the source from a git repository?
>> 
>> Not sure what you mean here. A git repo is a sequence of commits with some commits 'blessed' with tags, which are what are usually used to mark released versions. Revisions are not something that usually come up for git.
>> In Fink, a revision is the tracker for changes to an individual package at a certain source version. So if you have Version: 2.1.1 and then realize something needs to change in the package (a bug, new feature), but it's still using the same version from upstream, the Revision field is increased to note that the older description is now outdated.
>> 
> Many repos now have a ‘releases’ directory that is populated with tarballs of the tagged releases.
> So you can conveniently download directly from GitHub, but by default they have non-descriptive
> naming schemes like v%v.tar.gz. But that is easily handled by the SourceRename field as you
> described below.
> 
> Cheers,
> 						Derek
> 
> 
> 
> _______________________________________________
> Fink-devel mailing list
> [email protected]
> List archive:
> https://sourceforge.net/p/fink/mailman/fink-devel
> Subscription management:
> https://lists.sourceforge.net/lists/listinfo/fink-devel

_______________________________________________
Fink-devel mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel