Re: net/ntopng: version jump by an order of magnitude
On 9/20/18 5:32 AM, Kubilay Kocak wrote: > On 20/09/2018 6:40 am, Franco Fichtner wrote: >> Hi, >> >> Small question: >> >> https://github.com/freebsd/freebsd-ports/commit/0585180d >> >> ... has a typo in the version number which was an ISO date >> originally. Are we using this new date format now or is there >> going to be a PORTEPOCH amendment? > Terribly sorry I did not catch the typo before committing! > Up to the maintainer ultimately. > > To avoid PORTEPOCH, either the typo'd datestamp scheme (0XX for month) > would need to continue until 3.7, or an alternate scheme created that is > both meaningful and > than (pkg version -t old new) the current value. > > Or fix the typo and add PORTEPOCH. > > Personally, I'd go the first option as it's only a minor typo that > doesn't affect ongoing existing-scheme version updates, and is the more > transient of the two (PORTEPOCH lives forever, bad scheme only lasts > till 3.7). Yes, I think this is what I'll be doing. There seems to be no real harm in that. BTW they are skipping odd numbers, so next version is likely to be 3.8. -- Guido Falsi ___ 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: RUN_DEPENDS and portmaster
Am 19.09.18 um 14:25 schrieb Kurt Jaeger: > Hi! > >> Why is Ada only available on i386/amd64? > > Because nobody provided fixes for the build on other platforms up to now. And given that the only use of Ada in FreeBSD ports seems to be synth, it seems a lot easier to implement the synth functionality in some more portable (or at least readily available) language. There is nothing in Ada, that makes it specifically suitable for synth. The synth code consists mostly of string processing and program invocations. It uses Ada exception handling, but I did not spot anything that could not easily be implemented in any other language. In fact, due to the many invocations of external binaries, porting of synth to a shell seems sensible. I do not consider the time-outs on all the build phases a strict requirement, but even those could be implemented with shell mechanisms, The setup of the clean environment for the package builds is easy to extract and I have considered adding that feature to portmaster, to support building of ports that currently fail if a previous version is installed (generally caused by include paths that prefer installed headers over those in the sources of the new version). Regards, STefan ___ 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: net/ntopng: version jump by an order of magnitude
Hi Guido, > On 20. Sep 2018, at 9:02 AM, Guido Falsi wrote: > > Terribly sorry I did not catch the typo before committing! No worries, was just wondering about it to point out that going back to the proper date will not upgrade through package because the version number is smaller again. > BTW they are skipping odd numbers, so next version is likely to be 3.8. Alright. Thanks for the quick reply. :) Cheers, Franco ___ 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: net/ntopng: version jump by an order of magnitude
On Wed, Sep 19, 2018 at 9:32 PM Kubilay Kocak wrote: > > On 20/09/2018 6:40 am, Franco Fichtner wrote: > > Hi, > > > > Small question: > > > > https://github.com/freebsd/freebsd-ports/commit/0585180d > > > > ... has a typo in the version number which was an ISO date > > originally. Are we using this new date format now or is there > > going to be a PORTEPOCH amendment? > > Up to the maintainer ultimately. > > To avoid PORTEPOCH, either the typo'd datestamp scheme (0XX for month) > would need to continue until 3.7, or an alternate scheme created that is > both meaningful and > than (pkg version -t old new) the current value. > > Or fix the typo and add PORTEPOCH. > > Personally, I'd go the first option as it's only a minor typo that > doesn't affect ongoing existing-scheme version updates, and is the more > transient of the two (PORTEPOCH lives forever, bad scheme only lasts > till 3.7). > > > > > Cheers, > > Franco The 'd' is arbitrary. If a different, higher letter were used, the date could be fixed. # 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: net/ntopng: version jump by an order of magnitude
On 9/20/18 3:44 PM, Adam Weinberger wrote: > On Wed, Sep 19, 2018 at 9:32 PM Kubilay Kocak wrote: >> >> On 20/09/2018 6:40 am, Franco Fichtner wrote: >>> Hi, >>> >>> Small question: >>> >>> https://github.com/freebsd/freebsd-ports/commit/0585180d >>> >>> ... has a typo in the version number which was an ISO date >>> originally. Are we using this new date format now or is there >>> going to be a PORTEPOCH amendment? >> >> Up to the maintainer ultimately. >> >> To avoid PORTEPOCH, either the typo'd datestamp scheme (0XX for month) >> would need to continue until 3.7, or an alternate scheme created that is >> both meaningful and > than (pkg version -t old new) the current value. >> >> Or fix the typo and add PORTEPOCH. >> >> Personally, I'd go the first option as it's only a minor typo that >> doesn't affect ongoing existing-scheme version updates, and is the more >> transient of the two (PORTEPOCH lives forever, bad scheme only lasts >> till 3.7). >> >>> >>> Cheers, >>> Franco > > The 'd' is arbitrary. If a different, higher letter were used, the > date could be fixed. The d is what is suggested by the porter's handbook. While I could change it arbitrarily I think leaving the typo is more intuitive. Anyway no need to change anything till the next update. -- Guido Falsi ___ 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"
Gkrellm not building
I am using Freebsd 11.1 Release. Recently I wanted to upgrade gkrellm which I use on my fluxbox desktop. I normally build everything from ports and for the last week I have been trying to build gkrellm but it keeps giving the following error and quits: *portmaster sysutils/gkrellm===>>> Port directory: /usr/ports/sysutils/gkrellm===>>> Gathering distinfo list for installed ports===>>> Launching 'make checksum' for sysutils/gkrellm in background===>>> Gathering dependency list for sysutils/gkrellm from ports===>>> Initial dependency check complete for sysutils/gkrellm===>>> Starting build for sysutils/gkrellm <<<==>>> All dependencies are up to date===> Cleaning for gkrellm-1.2.13_11===> gkrellm-1.2.13_11 cannot install: Unknown component imlib.*** Error code 1Stop.make: stopped in /usr/ports/sysutils/gkrellm===>>> make build failed for sysutils/gkrellm===>>> Aborting update===>>> You can restart from the point of failure with this command line: portmaster sysutils/gkrellm * I tried looking up imlib in the ports and I got graphics/imlib2 which I built. But it has no effect on gkrellm. I cant find anything on imlib on google either. So I have no idea what should be done to get the code to build. I run portsnap everyday so my ports list is up to date. Any pointers are most welcome. Amit ___ 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"
