Solved Where is the tar.gz file location at in Makefile?

johnblue

johnblue

Using the gitup port as an example .. when I look at the Makefile it does not say anything about the location of a tar.gz file.

However, when I run make clean install it knows where to fetch the tar.gz:

Code: 
:/usr/ports/net/gitup # make clean install
===>  Cleaning for gitup-1.0
===>  License BSD2CLAUSE accepted by the user
===>   gitup-1.0 depends on file: /usr/local/sbin/pkg - found
=> johnmehr-gitup-1.0_GH0.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch https://codeload.github.com/johnmehr/gitup/tar.gz/1.0?dummy=/johnmehr-gitup-1.0_GH0.tar.gz
fetch: https://codeload.github.com/johnmehr/gitup/tar.gz/1.0?dummy=/johnmehr-gitup-1.0_GH0.tar.gz: size unknown
fetch: https://codeload.github.com/johnmehr/gitup/tar.gz/1.0?dummy=/johnmehr-gitup-1.0_GH0.tar.gz: size of remote file is not known
johnmehr-gitup-1.0_GH0.tar.gz                           32 kB  732 kBps    00s

Where is this URL stored at?
 
Code: 
PORTNAME=       gitup
DISTVERSION=    1.0

USE_GITHUB=     yes
GH_ACCOUNT=     johnmehr

That is what it is constructed from behind the scenes.
 
For this example port bsd.sites.mk line 354 it seems is where the suffix is created and then stuffed into a URL. Thanks Charlie_

Phishfry: I have been all up and down Chapter 5 looking for clues.

4.2 mentions:
Set the variable MASTER_SITES to reflect where the original tarball resides.
Click to expand...
.. and 5.4.2.2 table 4 infers that all kinds of URL's could be constructed but it does not say *where* it was being constructed at.

Guess that is why 5.4.2.2 is titled "Magic MASTER_SITES Macros"!

:D

Thanks all!
 
You must log in or register to reply here.
Back
Top