devel/stlink

[Dreamcat4]

On Sat, Aug 2, 2014 at 3:18 PM, Kurt Jaeger <lists at opsec.eu> wrote:

> > > Can you tell me where I get urllib2 for python on an 10.0-amd64 ?
> > >
> > > f10$ ./latest.sh
> > > Traceback (most recent call last):
> > >   File "getlatest.py", line 1, in <module>
> > >     import urllib2
> > > ImportError: No module named 'urllib2'
> >
> > Ah, I see, in my case it was installed with python27:
> > $ pkg which /usr/local/lib/python2.7/urllib2.py
> > /usr/local/lib/python2.7/urllib2.py was installed by package
> python27-2.7.8
>
> Thanks. Now, frankly, I have no easy idea on how to integrate this
> "get the latest from github" into a proper port.


> Probably some /usr/ports/Mk/ magic needs to be created for this
> to work in general.
>

It is always possible to download HEAD using this distfiles URL:

https://github.com/${PORTNAME}/${PORTNAME}/archive/master.tar.gz

The problem with doing that is then you must disable the checksum
"distinfo". There is no way to know what the hash of such archive file is
supposed to be. Since that archive file itself is being dynamically
generated from the most recent commit...

That is probably why all Ports (using master branch on github) are fixed to
some specific GH_COMMIT. Then from time-to-time you have to move up the
notch.

Good source code projects on github may maintain a 'stable' tracking
branch. Which makes updating the GH_COMMIT safe and very easy process. Of
course, that doesn't necessarily matter for data repositories, which may be
safe to use the latest master / HEAD always.

Would it be sufficient if we just commit the current "state",
> explain the process in the pkg-message and provide your scripts
> latest.sh and getlatest.py with a stlink-related name ?
>
> I know this is not purrrrfect 8-}
>
> --
> pi at opsec.eu            +49 171 3101372                         6 years to
> go !
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>