Google Magenta Portfiles Help Request for new py-note-seq port

[Jason Liu]

>
> > pypi has a version of 0.0.0, but the github repo has no official version
>> number or even tags, and it’s not clear which commit the pypi version has
>> used.
>>
>
> If upstream doesn't have a useful version number, you need to make one up.
> It should monotonically increase over time. It should change
> whenever the upstream source code you are installing from changes.
>

For ports I've submitted which don't have any version numbering in the
project's GitHub repo, I've been using the date of the commit as the
version number in the portfile... but don't try to use the GitHub commit
hash, since that is not a monotonically increasing number. So, for example,
if I submitted a port for a project's commit that occurred today, the
version number would be 20200704. Some of the MacPorts devs have indicated
to me that this date-based version number shouldn't be separated using
dashes or dots; it should just look like a single integer. Also, don't
include the commit's time in the version number string, only the date.

-- 
Jason Liu


On Sat, Jul 4, 2020 at 1:49 PM Joshua Root <jmr at macports.org> wrote:

> On 2020-7-5 01:20 , Steven Smith wrote:
> > Re: versioning, here’s the situation:
> >
> > pypi has a version of 0.0.0, but the github repo has no official version
> number or even tags, and it’s not clear which commit the pypi version has
> used.
> >
> > I prefer to build from a github repo because it contains tests and other
> useful things that the pypi distribution doesn’t have.
> >
> > In this situation, I specified the commit hash, set the version to be
> consistent with pypi’s, and set the revision to be the github commit date.
> >
> > Is there another preferred way in this situation?
>
> If upstream doesn't have a useful version number, you need to make one
> up. It should monotonically increase over time. It should change
> whenever the upstream source code you are installing from changes.
>
> Revision is a property of the port, not the upstream sources. It should
> start at 0 with each new upstream version, and increment whenever you
> make changes to the port that change the installed files, while still
> using the same upstream version.
>
> - Josh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20200704/85317a41/attachment.htm>