Re: SF mastersites

2017-10-28 Thread Adam Weinberger
> On 28 Oct, 2017, at 22:18, blubee blubeeme  wrote:
> 
> @MarkMillard
> 
> Thank you for explaining that. Like you said there's lots of stuff that's
> just not documented. How should I know that I should check the man page for
> Makefile? I appreciate the help with that at least I'll be better informed
> in the future.
> 
> Things like that should be in the porter handbook as subsections or
> something.

Not in the Porter's Handbook, but the FreeBSD Handbook has a whole page about 
manpages: 
https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/basics-more-information.html

Makefiles are written in make(1) syntax, but used only to execute other FreeBSD 
commands and utilities; it simply wouldn't be practical to list the manpages 
for each of them in the Porter's Handbook. FreeBSD works very hard to maintain 
manpages for nearly every utility, conf file, and important procedure.

# Adam


-- 
Adam Weinberger
ad...@adamw.org
https://www.adamw.org

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: SF mastersites

2017-10-28 Thread blubee blubeeme
@MarkMillard

Thank you for explaining that. Like you said there's lots of stuff that's
just not documented. How should I know that I should check the man page for
Makefile? I appreciate the help with that at least I'll be better informed
in the future.

Things like that should be in the porter handbook as subsections or
something.

On Sun, Oct 29, 2017 at 9:29 AM, Dave Horsfall  wrote:

> On Sat, 28 Oct 2017, Mark Millard wrote:
>
> ${NAME:tl} is Makefile notation even in Makefiles having nothing to do
>> with ports (or potentially even FreeBSD). There probably is lots of
>> involved Makefile notation not separately documented in
>> makefile-distfiles.html or other parts of porters-handbook/ .
>>
>
> I've been using "make" since the PWB days, and this is news...  The
> trouble is, one would have to suspect that this is yet another variant
> before looking for specific documentation (and I thought "gmake" was bad
> enough).
>
> At least my Makefiles and shell scripts will work anywhere; I don't make
> use of local "features".
>
> --
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will
> suffer."
>
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: SF mastersites

2017-10-28 Thread Dave Horsfall

On Sat, 28 Oct 2017, Mark Millard wrote:

${NAME:tl} is Makefile notation even in Makefiles having nothing to do 
with ports (or potentially even FreeBSD). There probably is lots of 
involved Makefile notation not separately documented in 
makefile-distfiles.html or other parts of porters-handbook/ .


I've been using "make" since the PWB days, and this is news...  The 
trouble is, one would have to suspect that this is yet another variant 
before looking for specific documentation (and I thought "gmake" was bad 
enough).


At least my Makefiles and shell scripts will work anywhere; I don't make
use of local "features".

--
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: SF mastersites

2017-10-28 Thread Mark Millard
blubee blubeeme gurenchan at gmail.com wrote on
Sat Oct 28 05:33:38 UTC 2017:

> what does [:tl] even mean here? There's nothing about it on the whole page:
> https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.html

Also in a later message:

> thanks for that tip but how would I know to look at man [1 make] for
> something like that?


${NAME:tl} is Makefile notation even in Makefiles having nothing to
do with ports (or potentially even FreeBSD). There probably is lots
of involved Makefile notation not separately documented in
makefile-distfiles.html or other parts of porters-handbook/ .

Generally on BSD's, Linux's, and the like the Makefile notation
is documented in the man page for the make variation in use
(make, gmake, fmake, etc.).

Across types of systems "make" can vary which variant it refers
to. So, various man pages for "make" can disagree. The one in
the environment in question needs to be consulted unless one
knows an alternate name as used in an alternate environment.

So many standards to choose from. . .

===
Mark Millard
markmi at dsl-only.net

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: SF mastersites

2017-10-28 Thread Kurt Jaeger
Hi!

> thanks for that tip but how would I know to look at man [1 make] for
> something like that?

The BSD man pages in general are very detailed. So if a tool
has an issue, looking at the man page of the tool might help.

Yes, I'm still surprised about all the features bsd make has, but
it's a real feature monster.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: SF mastersites

2017-10-28 Thread blubee blubeeme
thanks for that tip but how would I know to look at man [1 make] for
something like that?

On Sat, Oct 28, 2017 at 2:38 PM, Herbert J. Skuhra 
wrote:

> On Sat, 28 Oct 2017 07:33:36 +0200,
> blubee blubeeme  wrote:
> >
> > I literally copy the entire url and add it to master_sites and it doesn't
> > work!
> >
> > what does [:tl] even mean here? There's nothing about it on the whole
> page:
> > https://www.freebsd.org/doc/en/books/porters-handbook/
> makefile-distfiles.html
>
> % man 1 make
>
>   :tl  Converts variable to lower-case letters.
>
> --
> Herbert
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: SF mastersites

2017-10-28 Thread Herbert J. Skuhra
On Sat, 28 Oct 2017 07:33:36 +0200,
blubee blubeeme  wrote:
> 
> I literally copy the entire url and add it to master_sites and it doesn't
> work!
> 
> what does [:tl] even mean here? There's nothing about it on the whole page:
> https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.html

% man 1 make
 
  :tl  Converts variable to lower-case letters.

--
Herbert
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: SF mastersites

2017-10-27 Thread blubee blubeeme
I literally copy the entire url and add it to master_sites and it doesn't
work!

what does [:tl] even mean here? There's nothing about it on the whole page:
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.html

SF ${PORTNAME:tl}/${PORTNAME:tl}/${PORTVERSION}
MASTER_SITES= SF/spacenav/files/spacenav%20library%20%28SDK%29/
DISTNAME= libspnav-${PORTVERSION}

=> libspnav-0.2.3.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch
https://downloads.sourceforge.net/project/spacenav/files/spacenav%20library%20%28SDK%29/libspnav-0.2.3.tar.gz
fetch:
https://downloads.sourceforge.net/project/spacenav/files/spacenav%20library%20%28SDK%29/libspnav-0.2.3.tar.gz:
Not Found
=> Attempting to fetch
https://cytranet.dl.sourceforge.net/project/spacenav/files/spacenav%20library%20%28SDK%29/libspnav-0.2.3.tar.gz
fetch:
https://cytranet.dl.sourceforge.net/project/spacenav/files/spacenav%20library%20%28SDK%29/libspnav-0.2.3.tar.gz:
Not Found
=> Attempting to fetch
https://excellmedia.dl.sourceforge.net/project/spacenav/files/spacenav%20library%20%28SDK%29/libspnav-0.2.3.tar.gz

still giving me not found errors!


On Sat, Oct 28, 2017 at 1:06 PM, blubee blubeeme 
wrote:

> These SF mater_sites give me a real tough time trying to figure it out and
> try to find github mirrors whenever possible but I need to figure this out.
>
> I'm trying to download: https://sourceforge.net/projects/spacenav/
>
> PORTNAME= freespacenav
> PORTVERSION= 0.2.3
>
> MASTER_SITES= SF/spacenav
> DISTNAME= libspnav-${PORTVERSION}
>
> I would think the version above would work since it leads to:
> https://downloads.sourceforge.net/project/spacenav/libspnav-0.2.3.tar.gz
>
> but that doesn't work!
>
> The documentation on: https://www.freebsd.org/
> doc/en/books/porters-handbook/makefile-distfiles.html
> 5.4.2.2. Magic MASTER_SITES Macros
> also leaves me more confused that relieved.
>
> Can anyone help me sort this out?
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


SF mastersites

2017-10-27 Thread blubee blubeeme
These SF mater_sites give me a real tough time trying to figure it out and
try to find github mirrors whenever possible but I need to figure this out.

I'm trying to download: https://sourceforge.net/projects/spacenav/

PORTNAME= freespacenav
PORTVERSION= 0.2.3

MASTER_SITES= SF/spacenav
DISTNAME= libspnav-${PORTVERSION}

I would think the version above would work since it leads to:
https://downloads.sourceforge.net/project/spacenav/libspnav-0.2.3.tar.gz

but that doesn't work!

The documentation on:
https://www.freebsd.org/doc/en/books/porters-handbook/makefile-distfiles.html
5.4.2.2. Magic MASTER_SITES Macros
also leaves me more confused that relieved.

Can anyone help me sort this out?
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"