Re: [New Port] Working on Gitlab - Calling for Help and Ideas
Hello Chris,
I'm pretty busy ATM. But if you haven't already, *do* read:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
it addresses the questions you've asked fairly well.
As to rc(5), and config related files in ${PREFIX}/etc
there are a good number of working examples in net-mgmt, dns,
sysutils, and perhaps www, to draw from.
Hope this helps!
I already know the porters handbook, but i appreciate the pointer. Every
time i read it, i become more familiar with it :)
I believe my general purpose question, was not such a good idea. More
specific i have a bunch of questions. The installations guide
(https://github.com/gitlabhq/gitlab-recipes/blob/master/install/freebsd/freebsd-10.md)
defines a number of packages to install. But i don't believe this should
be dependencies.
With the following packages i have problems to figure out if they are
really needed:
- sudo
- bash
- icu
- cmake
- pkgconf
- logrotate
- postgresql94-server
- postfix
- nginx
I don't think that postgresql and nginx should be either a run or a
build-dependency. The admin of the server should decide, which webserver
he wants to run.
While postgresql seems mandatory, it's not clear which version is
needed. At the moment i used USES= pgsql.
Here a response by a user would save much time. Otherwise i just have to
try every combination. I've already set up a jail for this - but maybe
somebody has an idea.
Next question: should "gem install bundler --no-ri --no-rdoc" be done by
port-installation? Or not? Or with an rc-script for initialization?
The port requires an git-user and some directory under /home/git. Should
the port add this?
How to handle database initialization? rc-script or manual?
So - any advice or experience is helpful.
Greetings,
Torsten
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [New Port] Working on Gitlab - Calling for Help and Ideas
On 23/04/2015 5:30 PM, Torsten Zuehlsdorff wrote:
> Hello Chris,
>
>> I'm pretty busy ATM. But if you haven't already, *do* read:
>> https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
>> it addresses the questions you've asked fairly well.
>> As to rc(5), and config related files in ${PREFIX}/etc
>> there are a good number of working examples in net-mgmt, dns,
>> sysutils, and perhaps www, to draw from.
>>
>> Hope this helps!
>
> I already know the porters handbook, but i appreciate the pointer. Every
> time i read it, i become more familiar with it :)
>
> I believe my general purpose question, was not such a good idea. More
> specific i have a bunch of questions. The installations guide
> (https://github.com/gitlabhq/gitlab-recipes/blob/master/install/freebsd/freebsd-10.md)
> defines a number of packages to install. But i don't believe this should
> be dependencies.
>
> With the following packages i have problems to figure out if they are
> really needed:
> - sudo
> - bash
> - icu
> - cmake
> - pkgconf
> - logrotate
> - postgresql94-server
> - postfix
> - nginx
>
> I don't think that postgresql and nginx should be either a run or a
> build-dependency. The admin of the server should decide, which webserver
> he wants to run.
> While postgresql seems mandatory, it's not clear which version is
> needed. At the moment i used USES= pgsql.
>
> Here a response by a user would save much time. Otherwise i just have to
> try every combination. I've already set up a jail for this - but maybe
> somebody has an idea.
>
> Next question: should "gem install bundler --no-ri --no-rdoc" be done by
> port-installation? Or not? Or with an rc-script for initialization?
>
> The port requires an git-user and some directory under /home/git. Should
> the port add this?
>
> How to handle database initialization? rc-script or manual?
>
> So - any advice or experience is helpful.
>
Hi Torsten,
I know that a couple of people have looked at creating a gitlab port in the
past, and possibly in progress. It might worthwhile catching up with them ..
Try Johannes (xmj) who's also on IRC (freenode/efnet), who should be able to at
least point you in the right direction and catch you up on his experience with
Gitlab.
Thanks for getting involved!
Koobs
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [New Port] Working on Gitlab - Calling for Help and Ideas
Hello Kubilay,
I'm pretty busy ATM. But if you haven't already, *do* read:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
it addresses the questions you've asked fairly well.
As to rc(5), and config related files in ${PREFIX}/etc
there are a good number of working examples in net-mgmt, dns,
sysutils, and perhaps www, to draw from.
Hope this helps!
I already know the porters handbook, but i appreciate the pointer. Every
time i read it, i become more familiar with it :)
I believe my general purpose question, was not such a good idea. More
specific i have a bunch of questions. The installations guide
(https://github.com/gitlabhq/gitlab-recipes/blob/master/install/freebsd/freebsd-10.md)
defines a number of packages to install. But i don't believe this should
be dependencies.
With the following packages i have problems to figure out if they are
really needed:
- sudo
- bash
- icu
- cmake
- pkgconf
- logrotate
- postgresql94-server
- postfix
- nginx
I don't think that postgresql and nginx should be either a run or a
build-dependency. The admin of the server should decide, which webserver
he wants to run.
While postgresql seems mandatory, it's not clear which version is
needed. At the moment i used USES= pgsql.
Here a response by a user would save much time. Otherwise i just have to
try every combination. I've already set up a jail for this - but maybe
somebody has an idea.
Next question: should "gem install bundler --no-ri --no-rdoc" be done by
port-installation? Or not? Or with an rc-script for initialization?
The port requires an git-user and some directory under /home/git. Should
the port add this?
How to handle database initialization? rc-script or manual?
So - any advice or experience is helpful.
Hi Torsten,
I know that a couple of people have looked at creating a gitlab port in the
past, and possibly in progress. It might worthwhile catching up with them ..
I've tried to find some others, but without success. It seems that there
was a port which is no longer available :/
Try Johannes (xmj) who's also on IRC (freenode/efnet), who should be able to at
least point you in the right direction and catch you up on his experience with
Gitlab.
Thanks for the pointer, i've emailed him some minutes ago. :)
Thanks for getting involved!
Thanks for your help!
Greetings,
Torsten
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: databases/mysql-connector-java: Looks broken to me
I was not informed of the discussion, because as I had stated you need to cc my email should you wish that I receive notification of your answers. Anyway, the purpose of my attempt to use the port was to try and solve a long-standing problem: I cannot find a way to connect libreoffice-base to mysql. LO Base can connect to external DB server, if a proper driver is supplied. JDBC is a more appropriate driver than ODBC, but a driver LO can use on FreeBSD does not seem to exist. The LO add-ons page has JDBC for Lİnux, but that extension does not install on FreeBSD. I was able to connect math/gnumeric for example through the use of Gnome's DB connection component databases/libgda5-mysql, but that does not seem to work for libreoffice. As another example, KDE's Kexi program is also able to connect to the MySQL server. On the other hand, some solutions suggest installing "com.mysql.jdbc.Driver" from http://dev.mysql.com/downloads/connector/j/, but that does not make a whole lot of sense to me. Regards. -- FreeBSD_amd64_11-Current_RadeonKMS Please CC my email when responding, mail from list is not delivered. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
ftp/curl compiler error
I'm seeing this odd error when trying to compile ftp/curl configure: using CFLAGS: -I/usr/include -O2 -pipe -fstack-protector -fno-strict-aliasing configure: CFLAGS note: CFLAGS should only be used to specify C compiler flags, not include directories. Use CPPFLAGS for: -I/usr/include configure: WARNING: Continuing even with errors mentioned immediately above this line. checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for gcc... cc checking whether the C compiler works... no configure: error: in `/asp/obj/asp/git/ports/ftp/curl/work/curl-7.42.0': configure: error: C compiler cannot create executables * As a test, I placed "CPPFLAGS+= -I /usr/include" in /etc/make.conf, but no change with the error. * If I cd to /usr/obj/ports/ftp/curl/work/curl-7.42.0 and run make from within that folder, compile runs normally, but uses gcc checking for a BSD-compatible install... /usr/bin/install -c checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking how to run the C preprocessor... gcc -E checking whether build environment is sane... yes * "make USE_GCC=any -C ftp/curl" has no effect, I get same error. * Enabled options: CA_BUNDLE, COOKIES, IDN, PROXY, TLS_SRP, GSSAPI_BASE, THREADED_RESOLVER, OPENSSL. All other options off. Disabling a number of these options made no difference. -- FreeBSD_amd64_11-Current_RadeonKMS Please CC my email when responding, mail from list is not delivered. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ftp/curl compiler error
On 04/23/15 11:56, Beeblebrox via freebsd-ports wrote: I'm seeing this odd error when trying to compile ftp/curl configure: using CFLAGS: -I/usr/include -O2 -pipe -fstack-protector -fno-strict-aliasing configure: CFLAGS note: CFLAGS should only be used to specify C compiler flags, not include directories. Use CPPFLAGS for: -I/usr/include Do you have local changes in the port Makefile? CFLAGS in fresh /usr/ports/ftp/curl has no -I/usr/include configure: error: in `/asp/obj/asp/git/ports/ftp/curl/work/curl-7.42.0': configure: error: C compiler cannot create executables See for exact error: cd `make -V WRKSRC` fgrep -B 35 'C compiler cannot create executables' config.log ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ftp/curl compiler error
Thanks for the pointer. The problem was option setting GSSAPI_BASE, which should have been GSSAPI_HEIMDAL. I don't build krb5 in world, therefore lkrb5 does not exist on the system. This results in the mentioned error, which fgrep on config.log displays: configure:4218: checking whether the C compiler works configure:4240: cc -I/usr/include -O2 -pipe -fstack-protector -fno-strict-aliasing -I /usr/include -I/usr/include -I/usr/local/include -L/usr/lib -L/usr/lib -L/usr/local/lib -Wl,-rpath,/usr/local/lib -L/usr/local/lib -Wl,-rpath,/usr/local/lib -fstack-protector conftest.c -lkrb5 -lgssapi -lgssapi_krb5 -lkrb5 -lgssapi -lgssapi_krb5 >&5 /usr/bin/ld: cannot find -lkrb5 Thanks again for the help. -- FreeBSD_amd64_11-Current_RadeonKMS Please CC my email when responding, mail from list is not delivered. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [New Port] Working on Gitlab - Calling for Help and Ideas
On Thu, 23 Apr 2015 09:30:01 +0200 Torsten Zuehlsdorff
wrote
> Hello Chris,
>
> > I'm pretty busy ATM. But if you haven't already, *do* read:
> > https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
> > it addresses the questions you've asked fairly well.
> > As to rc(5), and config related files in ${PREFIX}/etc
> > there are a good number of working examples in net-mgmt, dns,
> > sysutils, and perhaps www, to draw from.
> >
> > Hope this helps!
>
> I already know the porters handbook, but i appreciate the pointer. Every
> time i read it, i become more familiar with it :)
Sure. Just checking. :)
>
> I believe my general purpose question, was not such a good idea. More
> specific i have a bunch of questions. The installations guide
> (https://github.com/gitlabhq/gitlab-recipes/blob/master/install/freebsd/freeb
> sd-10.md)
Hmm... this is *quite* a large package. With a lot of moving parts.
I think it even trumps Xorg. While it can be done. I'm not sure this
is an ideal candidate for a port...
> defines a number of packages to install. But i don't believe this
> should be dependencies.
Well. After the (your) port has completed install, it should be
nearly ready to "just work". Reading the article, it indicates all
of those as dependencies. Are you looking to create a port that is
a deviation, with a different list of dependencies?
>
> With the following packages i have problems to figure out if they are
> really needed:
> - sudo
sudo, su, gksu, ... -- *something* will be needed. What you choose
is up to you.
> - bash
Are the scripts that come with your port written for bash(1)? If
so, it (bash) will need to be installed.
> - icu
> - cmake
This will likely get installed somewhere down the line, anyway
> - pkgconf
Same here
> - logrotate
> - postgresql94-server
You'll need to determine the minimum version required (>=???)
> - postfix
> - nginx
All in all, the article seems to provide fairly specific instructions
for installing, and after fulfilling all the dependencies, the user
is still left with a substantial amount of configuration to do.
Are you looking to create those configurations, as well? Even
if so, much of it must still be performed specifically by, and
for the end users circumstances.
I'm still not convinced this is a good (port) candidate. But
there's no reason you can't prove me wrong. ;)
>
> I don't think that postgresql and nginx should be either a run or a
> build-dependency. The admin of the server should decide, which webserver
> he wants to run.
> While postgresql seems mandatory, it's not clear which version is
> needed. At the moment i used USES= pgsql.
>
> Here a response by a user would save much time. Otherwise i just have to
> try every combination. I've already set up a jail for this - but maybe
> somebody has an idea.
>
> Next question: should "gem install bundler --no-ri --no-rdoc" be done by
> port-installation? Or not? Or with an rc-script for initialization?
>
> The port requires an git-user and some directory under /home/git. Should
> the port add this?
>
> How to handle database initialization? rc-script or manual?
>
> So - any advice or experience is helpful.
>
> Greetings,
> Torsten
--Chris
--
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [New Port] Working on Gitlab - Calling for Help and Ideas
On 23.04.2015 17:11, Chris H wrote: I believe my general purpose question, was not such a good idea. More specific i have a bunch of questions. The installations guide (https://github.com/gitlabhq/gitlab-recipes/blob/master/install/freebsd/freeb sd-10.md) > Hmm... this is *quite* a large package. With a lot of moving parts. I think it even trumps Xorg. While it can be done. I'm not sure this is an ideal candidate for a port... > defines a number of packages to install. But i don't believe this should be dependencies. > Well. After the (your) port has completed install, it should be nearly ready to "just work". Reading the article, it indicates all of those as dependencies. Are you looking to create a port that is a deviation, with a different list of dependencies? Yes, because i don't think the article is right. logrotate for example. There is a configuration shipped with gitlab. But its neither an run nor an build-dependency. Logrotate is a very handy tool, which should be used. But gitlab will run without it. But i'm not sure if i should make its installation an option or if let the decision completely left. Many programs which creates (big) logs (in the long run) don't even mention logrotate. With the following packages i have problems to figure out if they are really needed: - sudo sudo, su, gksu, ... -- *something* will be needed. What you choose is up to you. Indeed. The article uses sudo for configuration. But i could not figure out, if gitlab itself needs sudo. I don't know any port which requires sudo for the configuration the administrator has to do. But i'm not sure if there is a part of gitlab which really needs it. I don't believe it, because the article do not mention any configuration of sudo for gitlab. - bash Are the scripts that come with your port written for bash(1)? If so, it (bash) will need to be installed. At the moment the are unwritten, but i would aim for sh or tcsh to minimize requirements. - postfix - nginx > All in all, the article seems to provide fairly specific instructions for installing, and after fulfilling all the dependencies, the user is still left with a substantial amount of configuration to do. Are you looking to create those configurations, as well? Even if so, much of it must still be performed specifically by, and for the end users circumstances. That is my problem. The article describes installation of different software just to get gitlab running. But that is not the purpose of a port. Setting up an email server with sql-backend is even more configuration and work than the initial work for gitlab. Also the article takes the user away its decisions. I really love nginx, but i could not find any specifics which makes it mandatory. The user easily can use apache, yaws or something other. At the moment i'm having more this kind of questions than the specific technical ones. They will follow ;) Greetings, Torsten ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: icinga2-2.3.3_1
Hi! Thanks again for maintaining the freebsd ports. Do you have any plans of upgrading to icinga2-2.4 soon? I got some issues that probably are fixed with the update. All the best. Ruud ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [New Port] Working on Gitlab - Calling for Help and Ideas
Le jeu 23 avr 15 à 17:47:16 +0200, Torsten Zuehlsdorff écrivait : > Also the article takes the user away its decisions. I really love nginx, > but i could not find any specifics which makes it mandatory. The user > easily can use apache, yaws or something other. ATM, you could choose a web server (Apache seems wellknown, but if you prefer nginx, go for it!). Soon, pkg will be enhanced to handle "provides / needs", and then you'll be able to just set "needs a webserver". Or if you have many time, you could provide a set of options. About the configuration, I would suggest: - provide sample config files (with comments when possible) - explain the first steps in pkg-message (or just explain which document to follow). Good luck! -- Th. Thomas. pgpu5nySfH1Dx.pgp Description: PGP signature
Re: ftp/curl compiler error
any pointers for me?
-O2 -pipe -march=native -fstack-protector -fno-strict-aliasing
-Qunused-arguments -pthread -MT libcurl_la-url.lo -MD -MP -MF
.deps/libcurl_la-url.Tpo -c -o libcurl_la-url.lo `test -f 'url.c' || echo
'./'`url.c
libtool: compile: cc -DHAVE_CONFIG_H -I../include/curl -I../include
-I../include -I../lib -I../lib -DBUILDING_LIBCURL -DCURL_HIDDEN_SYMBOLS
-fvisibility=hidden -O2 -pipe -march=native -fstack-protector
-fno-strict-aliasing -Qunused-arguments -pthread -MT libcurl_la-url.lo -MD
-MP -MF .deps/libcurl_la-url.Tpo -c url.c -fPIC -DPIC -o
.libs/libcurl_la-url.o
url.c:3216:34: error: no member named 'ntlm' in 'struct connectdata'
(wantNTLMhttp || check->ntlm.state != NTLMSTATE_NONE)) {
~ ^
1 error generated.
*** Error code 1
Enabled - cookies, ipv6, proxy, gssapi_none, threaded_resolver.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/ftp-curl-compiler-error-tp6006985p6007099.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ftp/curl compiler error
Jakub,
> url.c:3216:34: error: no member named 'ntlm' in 'struct connectdata'
> (wantNTLMhttp || check->ntlm.state != NTLMSTATE_NONE)) {
ntlm is a Heimdal module, which means the gssapi_none knob isn't quite working
as it should. I would suggest you try enabling one of the api knobs for now
until they get "none" working.
--
FreeBSD_amd64_11-Current_RadeonKMS
Please CC my email when responding, mail from list is not delivered.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
