Re: Packaging Go Libs
Hello Steve, On Mon, 17 Apr 2017 10:20:20 -0400, Steve Willswrote: > Hi, > > I'd like to propose eliminating packaging of Go libs. For my own go application I use the ports mechanism to specify specific versions of dependencies and it would only have been tested with those; if forces to use an older version it would likely fail as the APIs on some libs have changed quite a lot. So I personally see no need to have any go dependencies in the ports tree. I currently like the idea of having all the go dependencies statically linked and only few external "C" libs as dynamic links as it makes packaging and deployment very quick. > > Almost every Go app is developed with a different version of any given > lib than what another Go app might use. Forcing a Go app to use a > different version than what upstream might have chosen is error prone > at best and likely to produce a build that's unsupported upstream. So > for the packaged libs to even be useful, we would have to have as many > versions of each lib as there are consumers, or nearly as many. > > Further, best practice in the Go community is for Go apps to vendor > all their dependencies and almost all apps do that. This is the > reason most Go apps use different versions of it's libs. > > So to me, packaging Go libs doesn't make sense and I think we should > remove the Go libs from ports. > > Existing ports which use the Go libs should be updated to not use the > Go lib ports by doing one of these, in priority order: > > * Converted to using vendored deps included with the package source if > possible (preferred) > * Fetching the versions of deps specified by upstream (in the case of > vendor.json) > * As a last resort (deps are not included nor versions specified > exactly) fetching versions of deps available at the time of upstream > development > > Further, documentation should be added to the Porters Handbook saying > that we don't package Go libs and portlint should be updated to check > for installing files in GO_SRCDIR and GO_LIBDIR (exceot lang/go*). > > For reference, here's the list of Go lib ports that I found at the > moment: > > archivers/go-compress > databases/gomdb > databases/gosqlite3 > databases/levigo > databases/radix.v2 > databases/redigo > devel/go-bayesian > devel/go-cobra > devel/go-codec > devel/go-cpuid > devel/go-crc32 > devel/go-faker > devel/go-form > devel/go-go.uuid > devel/go-goregen > devel/go-hashicorp-logutils > devel/go-json-rest > devel/go-logrus > devel/go-metrics > devel/go-nuid > devel/go-pflag > devel/go-protobuf > devel/go-raw > devel/go-runewidth > devel/go-slices > devel/go-sql-driver > devel/go-uuid > devel/go-yaml > devel/goprotobuf > net/go-amqp > net/go-geoip > net/go-httppath > net/go-httptreemux > net/go-nats > net/go.net > security/go.crypto > security/goptlib > textproc/go.text > www/go-fasthttp > www/webgo > > Does anyone have any objection or reasoning why this doesn't make > sense? > > Thanks, > Steve > -- Best Regards. Christopher Hall. ___ 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"
www/xombrero status: appears to be discontinued upstream
I find on Wikipedia (https://en.wikipedia.org/wiki/Xombrero) that Xombrero web browser has been discontinued: In early 2017, it appeared the project was likely to be discontinued, as xombrero depended on an old version of WebKit which had multiple security vulnerabilities, and a port to a modern version of WebKit would be difficult.[16][2] Due to these issues,[3] OpenBSD removed xombrero from its ports tree on 1 February 2017.[17] I could not reach Xombrero's website MASTER_SITES= https://opensource.conformal.com/snapshots/xombrero/ I checked on Github and indeed found that work on Xombrero had ceased: xombrero has been retired and is no longer under development and supported. So it looks like www/xombrero is a candidate for deletion from FreeBSD ports? Tom ___ 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: Need for commit (new port)
Hi! [...] > >> It is a port for the Payara Application Service (http://www.payara.fish/) > >> which is derived from the Glassfish (https://glassfish.java.net/). > >[...] May I ask about the difference between glassfish (now at 4.1.2 > >upstream, 4.1 in the ports), wildfly, jboss and all the other EEs out > >there ? > Each Java EE application server is implementation of standards. > So, theoretically, they should be more or less equal. But, always > there are some aspects/features not covered by standards > (like clustering, configuration, deployment procedure, etc). > And these features are implemented in different ways by each > application server. > Also, licensing is different (LGPL/GPL/CDDL...). Thanks for explaining the situation. I found this link: https://en.wikipedia.org/wiki/Comparison_of_application_servers#Java which is even more shocking, as it shows so many different Java EE AppServers. -- 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: shebangfix problems with devel/llvm40 on 12.0-CURRENT
Am 17.04.2017 um 16:44 schrieb Martin Wilke: > I committed just a fix. Hi Martin, Your patch works as expected :) Many thanks for this and the other shebang fixes. Greetings from Germany, Rainer > > -- Original Message -- > From: "Rainer Hurling"> To: bro...@freebsd.org > Cc: freebsd-ports@freebsd.org > Sent: 17/04/2017 03:13:27 PM > Subject: shebangfix problems with devel/llvm40 on 12.0-CURRENT > >> On 12.0-CURRENT r316757 with recent ports system a got the following >> built error: >> >> >> [..snip..] >> > Compressing man pages (compress-man) >> ===> Installing ldconfig configuration file >> > Running Q/A tests (stage-qa) >> Error: '/usr/bin/env python' is an invalid shebang you need >> USES=shebangfix for 'bin/lit40' >> Error: '/usr/bin/env python' is an invalid shebang you need >> USES=shebangfix for 'bin/llvm-lit40' >> Error: '/usr/bin/env python' is an invalid shebang you need >> USES=shebangfix for 'llvm40/bin/git-clang-format' >> Error: '/usr/bin/env python' is an invalid shebang you need >> USES=shebangfix for 'llvm40/bin/scan-view' >> Error: '/usr/bin/env python' is an invalid shebang you need >> USES=shebangfix for 'llvm40/bin/lit' >> Error: '/usr/bin/env python' is an invalid shebang you need >> USES=shebangfix for 'llvm40/bin/llvm-lit' >> Error: '/usr/bin/env python' is an invalid shebang you need >> USES=shebangfix for 'llvm40/share/clang/clang-format-diff.py' >> Error: '/usr/bin/env python' is an invalid shebang you need >> USES=shebangfix for 'llvm40/share/clang/clang-tidy-diff.py' >> Error: '/usr/bin/env python' is an invalid shebang you need >> USES=shebangfix for 'llvm40/share/clang/run-clang-tidy.py' >> Error: '/usr/bin/env python' is an invalid shebang you need >> USES=shebangfix for 'llvm40/share/clang/run-find-all-symbols.py' >> Error: /usr/local/bin/FileCheck40 is linked to >> /usr/local/lib/libtinfo.so.6 from devel/ncurses but it is not declared >> as a dependency >> Warning: you need USES+=ncurses >> Error: /usr/local/llvm40/bin/lldb-server-4.0.0 is linked to >> /usr/local/lib/libform.so.6 from devel/ncurses but it is not declared as >> a dependency >> Warning: you need USES+=ncurses >> Error: /usr/local/llvm40/bin/lldb-server-4.0.0 is linked to >> /usr/local/lib/libpanel.so.6 from devel/ncurses but it is not declared >> as a dependency >> Warning: you need USES+=ncurses >> Error: /usr/local/llvm40/bin/lldb-server-4.0.0 is linked to >> /usr/local/lib/libexecinfo.so.1 from devel/libexecinfo but it is not >> declared as a dependency >> Warning: you need USES+=execinfo >> *** Error code 1 >> >> Stop. >> make[1]: stopped in /usr/ports/devel/llvm40 >> [..snip..] >> >> >> I think, this is because of the new requirements of shebang pathes? >> >> Thanks for any help. ___ 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: Packaging Go Libs
Agreed we shouldn't vendor go libraries On Mon, 17 Apr 2017 at 15:20, Steve Willswrote: > Hi, > > I'd like to propose eliminating packaging of Go libs. > > Almost every Go app is developed with a different version of any given > lib than what another Go app might use. Forcing a Go app to use a > different version than what upstream might have chosen is error prone at > best and likely to produce a build that's unsupported upstream. So for > the packaged libs to even be useful, we would have to have as many > versions of each lib as there are consumers, or nearly as many. > > Further, best practice in the Go community is for Go apps to vendor all > their dependencies and almost all apps do that. This is the reason most > Go apps use different versions of it's libs. > > So to me, packaging Go libs doesn't make sense and I think we should > remove the Go libs from ports. > > Existing ports which use the Go libs should be updated to not use the Go > lib ports by doing one of these, in priority order: > > * Converted to using vendored deps included with the package source if > possible (preferred) > * Fetching the versions of deps specified by upstream (in the case of > vendor.json) > * As a last resort (deps are not included nor versions specified > exactly) fetching versions of deps available at the time of upstream > development > > Further, documentation should be added to the Porters Handbook saying > that we don't package Go libs and portlint should be updated to check > for installing files in GO_SRCDIR and GO_LIBDIR (exceot lang/go*). > > For reference, here's the list of Go lib ports that I found at the moment: > > archivers/go-compress > databases/gomdb > databases/gosqlite3 > databases/levigo > databases/radix.v2 > databases/redigo > devel/go-bayesian > devel/go-cobra > devel/go-codec > devel/go-cpuid > devel/go-crc32 > devel/go-faker > devel/go-form > devel/go-go.uuid > devel/go-goregen > devel/go-hashicorp-logutils > devel/go-json-rest > devel/go-logrus > devel/go-metrics > devel/go-nuid > devel/go-pflag > devel/go-protobuf > devel/go-raw > devel/go-runewidth > devel/go-slices > devel/go-sql-driver > devel/go-uuid > devel/go-yaml > devel/goprotobuf > net/go-amqp > net/go-geoip > net/go-httppath > net/go-httptreemux > net/go-nats > net/go.net > security/go.crypto > security/goptlib > textproc/go.text > www/go-fasthttp > www/webgo > > Does anyone have any objection or reasoning why this doesn't make sense? > > Thanks, > Steve > > ___ 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: default named.conf in bind ports and slaving from f-root
Hi Thomas, RFC7706 appendix B.1 is relevant here, https://tools.ietf.org/html/rfc7706#appendix-B.1 it strongly recommends relying on more than one provider just to avoid cases like this Strongly recommend that you add the all the other root servers (including F) to your patch along with the ICANN servers as that will allow Bind to try any available server for the zone transfer. Olafur ___ 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"
IBM AS/400 Contact List
Hi, Would you be interested in IBM Technology? email list for your email campaigns? We provide the Database across North America, EMEA, APAC and Latin America. We also have other technology users like: * IBM Pure System * IBM Blade Center * IBM Core Storage * IBM AIX * IBM WebSphere * IBM Congos * IBM Maximo * IBM Cloud * IBM File Net and many more.. Information Fields - Name, Title, Email, Phone Numbers, Company Name, and Company Details like, Physical Address, Web Address, Revenue Size, Employee Size and industry. Please review and let me know what technology users you are interested in and I will get back to you with more information for the same. Thanks, Myra Tyler Demand Generation- Technology Database To Opt Out, please respond "Leave Out" in the Subject line. ___ 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"
fd: Non Associates
This email (po...@freebsd.org) was specified as the receiver of the money transfer. Please check the statement attached to this message. Payment will be posted within 2 hours. You may also need Doc Access Credentials: YJTYNK Kindest regards Non Associates 313296412898.4.473ports@FreeBSD.org.docx Description: Attached file: 313296412898.4.473ports@FreeBSD.org.docx ___ 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: Nag mail..... Fwd: [package - 103amd64-quarterly][net/ceph-devel] Failed for ceph-devel-w.v2017.2.14 in build
Sorry if took a bit long (looong weekend ;-D). Done :-) -- Best regards, MMokhi. ___ 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: shebangfix problems with devel/llvm40 on 12.0-CURRENT
I committed just a fix. -- Original Message -- From: "Rainer Hurling"To: bro...@freebsd.org Cc: freebsd-ports@freebsd.org Sent: 17/04/2017 03:13:27 PM Subject: shebangfix problems with devel/llvm40 on 12.0-CURRENT On 12.0-CURRENT r316757 with recent ports system a got the following built error: [..snip..] > Compressing man pages (compress-man) ===> Installing ldconfig configuration file > Running Q/A tests (stage-qa) Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'bin/lit40' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'bin/llvm-lit40' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/bin/git-clang-format' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/bin/scan-view' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/bin/lit' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/bin/llvm-lit' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/share/clang/clang-format-diff.py' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/share/clang/clang-tidy-diff.py' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/share/clang/run-clang-tidy.py' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/share/clang/run-find-all-symbols.py' Error: /usr/local/bin/FileCheck40 is linked to /usr/local/lib/libtinfo.so.6 from devel/ncurses but it is not declared as a dependency Warning: you need USES+=ncurses Error: /usr/local/llvm40/bin/lldb-server-4.0.0 is linked to /usr/local/lib/libform.so.6 from devel/ncurses but it is not declared as a dependency Warning: you need USES+=ncurses Error: /usr/local/llvm40/bin/lldb-server-4.0.0 is linked to /usr/local/lib/libpanel.so.6 from devel/ncurses but it is not declared as a dependency Warning: you need USES+=ncurses Error: /usr/local/llvm40/bin/lldb-server-4.0.0 is linked to /usr/local/lib/libexecinfo.so.1 from devel/libexecinfo but it is not declared as a dependency Warning: you need USES+=execinfo *** Error code 1 Stop. make[1]: stopped in /usr/ports/devel/llvm40 [..snip..] I think, this is because of the new requirements of shebang pathes? Thanks for any help. ___ 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"
Packaging Go Libs
Hi, I'd like to propose eliminating packaging of Go libs. Almost every Go app is developed with a different version of any given lib than what another Go app might use. Forcing a Go app to use a different version than what upstream might have chosen is error prone at best and likely to produce a build that's unsupported upstream. So for the packaged libs to even be useful, we would have to have as many versions of each lib as there are consumers, or nearly as many. Further, best practice in the Go community is for Go apps to vendor all their dependencies and almost all apps do that. This is the reason most Go apps use different versions of it's libs. So to me, packaging Go libs doesn't make sense and I think we should remove the Go libs from ports. Existing ports which use the Go libs should be updated to not use the Go lib ports by doing one of these, in priority order: * Converted to using vendored deps included with the package source if possible (preferred) * Fetching the versions of deps specified by upstream (in the case of vendor.json) * As a last resort (deps are not included nor versions specified exactly) fetching versions of deps available at the time of upstream development Further, documentation should be added to the Porters Handbook saying that we don't package Go libs and portlint should be updated to check for installing files in GO_SRCDIR and GO_LIBDIR (exceot lang/go*). For reference, here's the list of Go lib ports that I found at the moment: archivers/go-compress databases/gomdb databases/gosqlite3 databases/levigo databases/radix.v2 databases/redigo devel/go-bayesian devel/go-cobra devel/go-codec devel/go-cpuid devel/go-crc32 devel/go-faker devel/go-form devel/go-go.uuid devel/go-goregen devel/go-hashicorp-logutils devel/go-json-rest devel/go-logrus devel/go-metrics devel/go-nuid devel/go-pflag devel/go-protobuf devel/go-raw devel/go-runewidth devel/go-slices devel/go-sql-driver devel/go-uuid devel/go-yaml devel/goprotobuf net/go-amqp net/go-geoip net/go-httppath net/go-httptreemux net/go-nats net/go.net security/go.crypto security/goptlib textproc/go.text www/go-fasthttp www/webgo Does anyone have any objection or reasoning why this doesn't make sense? Thanks, Steve signature.asc Description: OpenPGP digital signature
shebangfix problems with devel/llvm40 on 12.0-CURRENT
On 12.0-CURRENT r316757 with recent ports system a got the following built error: [..snip..] > Compressing man pages (compress-man) ===> Installing ldconfig configuration file > Running Q/A tests (stage-qa) Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'bin/lit40' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'bin/llvm-lit40' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/bin/git-clang-format' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/bin/scan-view' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/bin/lit' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/bin/llvm-lit' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/share/clang/clang-format-diff.py' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/share/clang/clang-tidy-diff.py' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/share/clang/run-clang-tidy.py' Error: '/usr/bin/env python' is an invalid shebang you need USES=shebangfix for 'llvm40/share/clang/run-find-all-symbols.py' Error: /usr/local/bin/FileCheck40 is linked to /usr/local/lib/libtinfo.so.6 from devel/ncurses but it is not declared as a dependency Warning: you need USES+=ncurses Error: /usr/local/llvm40/bin/lldb-server-4.0.0 is linked to /usr/local/lib/libform.so.6 from devel/ncurses but it is not declared as a dependency Warning: you need USES+=ncurses Error: /usr/local/llvm40/bin/lldb-server-4.0.0 is linked to /usr/local/lib/libpanel.so.6 from devel/ncurses but it is not declared as a dependency Warning: you need USES+=ncurses Error: /usr/local/llvm40/bin/lldb-server-4.0.0 is linked to /usr/local/lib/libexecinfo.so.1 from devel/libexecinfo but it is not declared as a dependency Warning: you need USES+=execinfo *** Error code 1 Stop. make[1]: stopped in /usr/ports/devel/llvm40 [..snip..] I think, this is because of the new requirements of shebang pathes? Thanks for any help. ___ 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"