Re: Updating ports that require cclang33 almost comes to a standstill!
Leslie Jensen skrev 2014-07-16 11:21: Hello list. I'm experiencing a very slow build of clang33 It seems that it's when building clang33/work/llvm-3.3 that is slows down. Using top I can see that my system is almost idle, 99,4, and cc1plus has two processes using WCPU at 1,80% and 0.10% I'm wondering if it's normal behaviour and I just have to sit it out? uname 9.1-RELEASE-p5 Thanks /Leslie ___ 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 First it stopped with this message. llvm[2]: Building Release Archive Library libclangARCMigrate.a gmake[2]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/lib/ARCMigrate' gmake[1]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/lib' gmake: *** [all] Error 1 === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/lang/clang33. *** [build] Error code 1 Stop in /usr/ports/lang/clang33. === make build failed for lang/clang33 === Aborting update Then I set MAKE_JOBS_UNSAFE=yes in /etc/make.conf and got this result. ase/RecursiveASTVisitorTest.d.tmp: No such file or directory gmake[2]: *** [/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling/Release/RecursiveASTVisitorTest.o] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling' gmake[1]: *** [Tooling/.makeall] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests' gmake: *** [all] Error 1 *** [do-build] Error code 1 Stop in /usr/ports/lang/clang33. *** [build] Error code 1 Stop in /usr/ports/lang/clang33. === make build failed for lang/clang33 === Aborting update /Leslie ___ 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: pkg-devel goes mad on 11-CURRENT with last repository update
On Thu, Jul 17, 2014 at 12:11:19AM +0400, Lev Serebryakov wrote: Hello, FreeBSD. I'm using 11-CURRENT (amd64) on my laptop and trying hard to use binary packages with pkg-devel. But attempt to upgrade installed packages goes crazy today. It trys to install ALL versions of gcc, ALL versions of subversion and many other unneeded packages! I'm using latest pkg-devel 1.3.0.r1. List of packages installed (pkg info output) and pkg upgrade output are attached. (THREES installed versions of gcc is another sad story, of course). Please try pkg-devel RC2. It should be fixed there. pgpoiU4DZY3cB.pgp Description: PGP signature
[QAT] 361966: 4x leftovers
1: Stagify. 2: USES=tar:bzip2. Approved by:portmgr@ (blanket) - Build ID: 20140715163800-54141 Job owner: vani...@freebsd.org Buildtime: 40 hours Enddate: Thu, 17 Jul 2014 08:31:46 GMT Revision: 361966 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=361966 - Port:multimedia/kdenlive 0.9.6_3 Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~vani...@freebsd.org/20140715163800-54141-377402/kdenlive-0.9.6_3.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~vani...@freebsd.org/20140715163800-54141-377403/kdenlive-0.9.6_3.log Buildgroup: 9.2-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~vani...@freebsd.org/20140715163800-54141-377404/kdenlive-0.9.6_3.log Buildgroup: 9.2-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~vani...@freebsd.org/20140715163800-54141-377405/kdenlive-0.9.6_3.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140715163800-54141 redports https://qat.redports.org/ ___ 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
[CFT] new libdrm with old xorg
Hi all, I need some testers to have one unique libdrm what ever version xorg is used, we know the newer version works properly with newer xorg, I have been testing so far with old xorg and everything seems to work ootb. Can anyone test and tell me if that works? basically before and after the update nothing should have changed. In particular I'm interested in testers for: FreeBSD 8 FreeBSD 9 http://people.freebsd.org/~bapt/drm.diff regards, Bapt pgpxdsZVMDQAI.pgp Description: PGP signature
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ lang/atlast | 1.2 | 2.0 +-+ www/linkchecker | 9.2 | 9.3 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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: Help with port test
On 07/15/14 06:36, Stefan Esser wrote: What does this mean? You are trying to delete the directory /usr/local, which is part of the base system. Just remove '@unexec rmdir /usr/local ...' from pkg-plist ... Hello Stefan. For some reason I didn't get your message and I see it only now... Of course I have no such line in pkg-plist. Actually both grep unexec pkg-plist and grep /usr/local pkg-plist give no match. bye Thanks av. ___ 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
Messa-7.6.1 is Missing
Or why has it been moved into: ftp.freedesktop.org/pub/mesa/7.6.1/ Hope you have a GREAT Day, after sorting out the the errors you lot sent us! Dr Sean J. Strand -- D.Sc ESA, Ph.D ESA, MBA T.Can, ++. ___ 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: Updating ports that require cclang33 almost comes to a standstill!
Dimitry Andric skrev 2014-07-17 00:10: On 16 Jul 2014, at 11:21, Leslie Jensen jensen.les...@gmail.com wrote: Hello list. I'm experiencing a very slow build of clang33 It seems that it's when building clang33/work/llvm-3.3 that is slows down. Using top I can see that my system is almost idle, 99,4, and cc1plus has two processes using WCPU at 1,80% and 0.10% cc1plus is actually gcc's C++ compiler, so clang isn't to blame here. :) Isn't there anything else going on, like linking (look for any 'ld' processes)? Or is the machine short on RAM (look at swap usage in top)? -Dimitry When the machine is idle these are the values. Mem: 27M Active, 236M Inact, 173M Wired, 10M Cache, 58M Buf, 21M Free Swap: 971M Total, 53M Used, 918M Free, 5% Inuse /Leslie ___ 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: Updating ports that require cclang33 almost comes to a standstill!
On Thu, Jul 17, 2014 at 02:54:09PM +0200, Leslie Jensen wrote: Dimitry Andric skrev 2014-07-17 00:10: On 16 Jul 2014, at 11:21, Leslie Jensen jensen.les...@gmail.com wrote: Hello list. I'm experiencing a very slow build of clang33 It seems that it's when building clang33/work/llvm-3.3 that is slows down. Using top I can see that my system is almost idle, 99,4, and cc1plus has two processes using WCPU at 1,80% and 0.10% cc1plus is actually gcc's C++ compiler, so clang isn't to blame here. :) Isn't there anything else going on, like linking (look for any 'ld' processes)? Or is the machine short on RAM (look at swap usage in top)? -Dimitry When the machine is idle these are the values. Mem: 27M Active, 236M Inact, 173M Wired, 10M Cache, 58M Buf, 21M Free Swap: 971M Total, 53M Used, 918M Free, 5% Inuse I suspect you need more swap. I'd recommend installing clang33 as a binary package. -- Brooks pgplwcKBuaavY.pgp Description: PGP signature
HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
Hi, I attend a lot of different Meetup groups in the San Francisco Bay Area / Silicon Valley. What I am seeing is the following usage pattern for new developers, especially for web apps and cloud applications. (1) On their desktop/laptop, they will generally be using a Mac running OS X. This is their desktop Unix environment. This seems to be true of almost 90% of the people that I meet. The 10% of people who run a PC laptop, will mostly be running Windows. Very few seem to run Linux on their laptops, but if they do, it will likely be Ubuntu Linux. (2) For their deployed application, generally they will deploy to a Linux environment on a server. These days, the server will very likely be in a cloud environment: Amazon, Rackspace, Heroku. For (1), encouraging people to move away from a Mac to FreeBSD for their desktop environment is a tough sell. Apple is a multi-billion dollar company, and they make beautiful hardware, and software with a fantastic end-user experience. The PC-BSD project is fighting the good fight in terms of making a usable FreeBSD desktop, but its a touch battle to fight. For (2), encouraging people to move away from Linux to FreeBSD on the server, may be something where we can get more wins. I think we can do this by having more HOWTO articles on the FreeBSD web page that explain the following: (1) We need a HOWTO article that explains for each command using apt or yum for installing packages, how can I do the same thing using pkg. Even if we have a web page with a table, contrasting the apt/yum commands, and pkg commands, that would be super useful. A lot of folks have moved away from FreeBSD, purely because they are sick of pkg_add. We need to explain to folks that we have something better, that is quite competitive to apt/yum, and it is easy to use. (2) We need a HOWTO article that explains how to set up a FreeBSD environment with some of the major cloud providers, i.e. Amazon, Rackspace, Microsoft Azure, etc. Do we have such articles today, or is anybody working on something like that? I think if we had these two HOWTO articles today, and we could aggressively point people at them, this would be a huge win for expanding the number of people who try out FreeBSD for modern server applications. -- Craig ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; 5) .. and then we need examples of actually deploying useful scenarios, like so here's what you type to get django working right, here's how you get a default memcached that works well, here's how you bring up node.js, etc. 6) Then make VMs of the above so people can just clone and install them. -a On 17 July 2014 11:25, Craig Rodrigues rodr...@freebsd.org wrote: Hi, I attend a lot of different Meetup groups in the San Francisco Bay Area / Silicon Valley. What I am seeing is the following usage pattern for new developers, especially for web apps and cloud applications. (1) On their desktop/laptop, they will generally be using a Mac running OS X. This is their desktop Unix environment. This seems to be true of almost 90% of the people that I meet. The 10% of people who run a PC laptop, will mostly be running Windows. Very few seem to run Linux on their laptops, but if they do, it will likely be Ubuntu Linux. (2) For their deployed application, generally they will deploy to a Linux environment on a server. These days, the server will very likely be in a cloud environment: Amazon, Rackspace, Heroku. For (1), encouraging people to move away from a Mac to FreeBSD for their desktop environment is a tough sell. Apple is a multi-billion dollar company, and they make beautiful hardware, and software with a fantastic end-user experience. The PC-BSD project is fighting the good fight in terms of making a usable FreeBSD desktop, but its a touch battle to fight. For (2), encouraging people to move away from Linux to FreeBSD on the server, may be something where we can get more wins. I think we can do this by having more HOWTO articles on the FreeBSD web page that explain the following: (1) We need a HOWTO article that explains for each command using apt or yum for installing packages, how can I do the same thing using pkg. Even if we have a web page with a table, contrasting the apt/yum commands, and pkg commands, that would be super useful. A lot of folks have moved away from FreeBSD, purely because they are sick of pkg_add. We need to explain to folks that we have something better, that is quite competitive to apt/yum, and it is easy to use. (2) We need a HOWTO article that explains how to set up a FreeBSD environment with some of the major cloud providers, i.e. Amazon, Rackspace, Microsoft Azure, etc. Do we have such articles today, or is anybody working on something like that? I think if we had these two HOWTO articles today, and we could aggressively point people at them, this would be a huge win for expanding the number of people who try out FreeBSD for modern server applications. -- Craig ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ 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: upgrading devel/p5-subversion fails
On Wed, 16 Jul 2014 23:52:38 +0200
Herbert J. Skuhra hsku...@eumx.net wrote:
On Wed, 16 Jul 2014 22:40:36 +0200
Serpent7776 wrote:
On Wed, 16 Jul 2014 22:11:58 +0200
Herbert J. Skuhra hsku...@eumx.net wrote:
On Wed, 16 Jul 2014 21:12:23 +0200
Serpent7776 wrote:
On Tue, 15 Jul 2014 14:51:42 -0700
Kevin Oberman rkober...@gmail.com wrote:
On Tue, Jul 15, 2014 at 2:11 PM, Herbert J. Skuhra hsku...@eumx.net
wrote:
On Tue, 15 Jul 2014 22:42:38 +0200
Serpent7776 wrote:
Hello,
I'm trying to upgrade p5-subversion, but I got error
sed: /usr/local/lib/libsqlite3.la: No such file or directory
libtool: link: `/usr/local/lib/libsqlite3.la' is not a valid
libtool
archive
*** [subversion/bindings/swig/perl/libsvn_swig_perl/
libsvn_swig_perl-1.la]
Error code 1 1 error
=== Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the
failure
to
the maintainer.
*** [do-build] Error code 1
Stop in /usr/ports/devel/p5-subversion.
Full output of portmaster p5-subversion available here:
http://pastie.org/private/ysbvkwqnppzqvangdqmew
File /usr/local/lib/libsqlite3.la does not exists.
I tried rebuilding sqlite3 and deleting p5-subversion before
reinstalling, but
this does not work.
My system is
# uname -a
FreeBSD DaemON.home 9.2-RELEASE-p10 FreeBSD 9.2-RELEASE-p10 #0:
Tue Jul
8
10:48:24 UTC 2014
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64
Have you tried to rebuild subversion before upgrading p5-subversion?
Have you tried to run 'portmaster -r sqlite3'?
Make sure that your portstree is up-to-date.
Looks like databases/sqlite3/Makefile has USES= pathfix libtool. By
default that will not install .la files. Normally they are only
needed during the build of the port, but it looks like libsqlite3.la
is an exception.
Try editing the Makefile to:
USES= pathfix libtool:keepla
and see if that fixes the problem.
Changing
USES= pathfix libtool
to
USES= pathfix libtool:keepla
Revert this again!
There is obviously a reason why the Makefile uses libtool and not
libtool:keepla!
r359585 | miwi | 2014-06-27 19:17:31 +0200 (Fri, 27 Jun 2014) | 4 lines
- Use proper stripping
- Don't keep la file since shlib got downgraded in r359529
- Bump PORTREVISION
You have obviously ignored my advice! After this change you have to
rebuild subversion! ('portmaster -r sqlite3' should rebuild subversion!)
Then p5-subversion builds fine.
--
Herbert
I'm running portmaster -r sqlite3 right now. I just wanted to try to change
makefile first to see if it helps, because it was quicker than rebuilding
~60 ports.
If only p5-subversion is affected, then try to rebuild only
devel/subversion before building devel/p5-subversion.
--
Herbert
I tried rebuilding sqlite3, subversion and libtool, but p5-subversion still
fails. I've noticed something odd though:
running make the first time in devel/p5-subversion gives
sed: /usr/local/lib/libsqlite3.la: No such file or directory
libtool: link: `/usr/local/lib/libsqlite3.la' is not a valid libtool archive
*** [subversion/bindings/swig/perl/libsvn_swig_perl/libsvn_swig_perl-1.la]
Error code 1
1 error
When I run make again build fails with different error:
install: .libs/libsvn_swig_perl-1.lai: No such file or directory
*** [install-swig-pl-lib] Error code 71
Stop in /usr/ports/devel/p5-subversion/work/subversion-1.8.9.
*** [do-install] Error code 1
Full output here: http://pastie.org/9400782
Don't know if it's important, but I use perl 5.16.
Maybe there is something wrong with libtool on my system?
Thanks
--
//Serpent7776
___
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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; I disagree on this. For network services on linux ( apart from ssh ), I want that started very seldom. But I do want the package installed so that when I need it, it is there. Having it autostart as part of being installed is breaking KISS and in some way unix philosophy: I asked for something to be installed, not installed and autostarted. 5) .. and then we need examples of actually deploying useful scenarios, like so here's what you type to get django working right, here's how you get a default memcached that works well, here's how you bring up node.js, etc. Oh yes. I think that quite a few packages have default options that make them unsuitable for out-of-box usage, ie some lack the sane default dbi-stuff and so on. 6) Then make VMs of the above so people can just clone and install them. At least zfs-datasets ready to be run as jails would be really good too. /A -a On 17 July 2014 11:25, Craig Rodrigues rodr...@freebsd.org wrote: Hi, I attend a lot of different Meetup groups in the San Francisco Bay Area / Silicon Valley. What I am seeing is the following usage pattern for new developers, especially for web apps and cloud applications. (1) On their desktop/laptop, they will generally be using a Mac running OS X. This is their desktop Unix environment. This seems to be true of almost 90% of the people that I meet. The 10% of people who run a PC laptop, will mostly be running Windows. Very few seem to run Linux on their laptops, but if they do, it will likely be Ubuntu Linux. (2) For their deployed application, generally they will deploy to a Linux environment on a server. These days, the server will very likely be in a cloud environment: Amazon, Rackspace, Heroku. For (1), encouraging people to move away from a Mac to FreeBSD for their desktop environment is a tough sell. Apple is a multi-billion dollar company, and they make beautiful hardware, and software with a fantastic end-user experience. The PC-BSD project is fighting the good fight in terms of making a usable FreeBSD desktop, but its a touch battle to fight. For (2), encouraging people to move away from Linux to FreeBSD on the server, may be something where we can get more wins. I think we can do this by having more HOWTO articles on the FreeBSD web page that explain the following: (1) We need a HOWTO article that explains for each command using apt or yum for installing packages, how can I do the same thing using pkg. Even if we have a web page with a table, contrasting the apt/yum commands, and pkg commands, that would be super useful. A lot of folks have moved away from FreeBSD, purely because they are sick of pkg_add. We need to explain to folks that we have something better, that is quite competitive to apt/yum, and it is easy to use. (2) We need a HOWTO article that explains how to set up a FreeBSD environment with some of the major cloud providers, i.e. Amazon, Rackspace, Microsoft Azure, etc. Do we have such articles today, or is anybody working on something like that? I think if we had these two HOWTO articles today, and we could aggressively point people at them, this would be a huge win for expanding the number of people who try out FreeBSD for modern server applications. -- Craig ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-curr...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 12:57, Andreas Nilsson andrn...@gmail.com wrote: On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; I disagree on this. For network services on linux ( apart from ssh ), I want that started very seldom. But I do want the package installed so that when I need it, it is there. Having it autostart as part of being installed is breaking KISS and in some way unix philosophy: I asked for something to be installed, not installed and autostarted. That's cool. We can disagree on that. But the fact that you have to edit a file to enable things and hope you get the right start entry in /etc/rc.conf or /usr/local/etc/rc.conf, or wherever you put it is, is a pain. -a ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Regards, Alberto Mijares ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? -a ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 07/17/14 13:12, Adrian Chadd wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? Aren't sysrc(8) and service(8) for this kind of stuff? ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 3:42 PM, Adrian Chadd adr...@freebsd.org wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? # service appname onestart For the rest, read the manual and understand your OS. ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar npar...@gmail.com wrote:
On 07/17/14 13:12, Adrian Chadd wrote:
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
wrote:
Hi!
3) The binary packages need to work out of the box
4) .. which means, when you do things like pkg install apache, it
can't just be installed and not be enabled, because that's a bit of a
problem;
No. Please NEVER do that! The user must be able to edit the files and
start the service by himself.
Cool, so what's the single line command needed to type in to start a
given package service?
Aren't sysrc(8) and service(8) for this kind of stuff?
They sure are.
Well, pkg install $service ; sysrc ${service}_enable=YES would do.
Although some services have different names than the packge, which is sort
of annoying.
I wouldn't mind though if pkg via dialog or some such mechanism asked if
wanted it enabled. Or via pkg-message told me howto enable it.
/A
___
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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 13:15, Navdeep Parhar npar...@gmail.com wrote: On 07/17/14 13:12, Adrian Chadd wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? Aren't sysrc(8) and service(8) for this kind of stuff? Yup, and if the default is going to be off, then you want the instructions to be type this in, not edit this file. There's odd things too, like oh look I installed xorg, but then I can't run it without enabling hald/dbus, then starting it.. oh wait, no mouse, so I have to reboot for them to come up right kind of crap. That's the kind of thing that turns people away. -a ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 10:21 PM, Adrian Chadd adr...@freebsd.org wrote: On 17 July 2014 13:15, Navdeep Parhar npar...@gmail.com wrote: On 07/17/14 13:12, Adrian Chadd wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? Aren't sysrc(8) and service(8) for this kind of stuff? Yup, and if the default is going to be off, then you want the instructions to be type this in, not edit this file. There's odd things too, like oh look I installed xorg, but then I can't run it without enabling hald/dbus, then starting it.. oh wait, no mouse, so I have to reboot for them to come up right kind of crap. That's the kind of thing that turns people away. But this is more of a desktop/laptop setup, right? If services had an option ( the ones provided via ports anyway) for autostart, and package sets for different use cases was provided, like server and desktop say, there could for desktop be the default to have the option set for autostart and for server the option would be to not autostart. /A ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar npar...@gmail.com wrote:
On 07/17/14 13:12, Adrian Chadd wrote:
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
wrote:
Hi!
3) The binary packages need to work out of the box
4) .. which means, when you do things like pkg install apache, it
can't just be installed and not be enabled, because that's a bit of a
problem;
No. Please NEVER do that! The user must be able to edit the files and
start the service by himself.
Cool, so what's the single line command needed to type in to start a
given package service?
Aren't sysrc(8) and service(8) for this kind of stuff?
They sure are.
Well, pkg install $service ; sysrc ${service}_enable=YES would do.
Although some services have different names than the packge, which is sort
of annoying.
Maybe service needs to be extended (seriously sysrc ${service}_enable=YES is
not user friendly) we have service -l that list the services, maybe a service
${service} on that create /etc/rc.conf.d/${service} with ${service}_enable=YES
in it and service ${service} off to remove it
maybe service -l could also be extended to show the current status (maybe with a
-v switch)
but for sure having the service off by default is a good idea :)
regards,
Bapt
pgpJFDQvbZfZe.pgp
Description: PGP signature
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, 2014-07-17 at 13:21 -0700, Adrian Chadd wrote: On 17 July 2014 13:15, Navdeep Parhar npar...@gmail.com wrote: On 07/17/14 13:12, Adrian Chadd wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? Aren't sysrc(8) and service(8) for this kind of stuff? Yup, and if the default is going to be off, then you want the instructions to be type this in, not edit this file. There's odd things too, like oh look I installed xorg, but then I can't run it without enabling hald/dbus, then starting it.. oh wait, no mouse, so I have to reboot for them to come up right kind of crap. That's the kind of thing that turns people away. I see your point, and agree that there should be clear instructions after installing a port/package. Most ports I install already do a good job at this. But I would not like anything to autostart just because I install it. Prefer to enable rather than disable something, or worse, having it autostart without knowing. That's the kind of thing that turned me to FreeBSD :-) -a ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to freebsd-doc-unsubscr...@freebsd.org ___ 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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 01:21:32PM -0700, Adrian Chadd wrote: On 17 July 2014 13:15, Navdeep Parhar npar...@gmail.com wrote: On 07/17/14 13:12, Adrian Chadd wrote: On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote: On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; No. Please NEVER do that! The user must be able to edit the files and start the service by himself. Cool, so what's the single line command needed to type in to start a given package service? Aren't sysrc(8) and service(8) for this kind of stuff? Yup, and if the default is going to be off, then you want the instructions to be type this in, not edit this file. There's odd things too, like oh look I installed xorg, but then I can't run it without enabling hald/dbus, then starting it.. oh wait, no mouse, so I have to reboot for them to come up right kind of crap. yes that is why xorg needs to have devd instead of hal support by default :) regards, Bapt pgp006GaASOyO.pgp Description: PGP signature
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On 17 July 2014 13:54, Baptiste Daroussin b...@freebsd.org wrote:
On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar npar...@gmail.com wrote:
On 07/17/14 13:12, Adrian Chadd wrote:
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
wrote:
Hi!
3) The binary packages need to work out of the box
4) .. which means, when you do things like pkg install apache, it
can't just be installed and not be enabled, because that's a bit of a
problem;
No. Please NEVER do that! The user must be able to edit the files and
start the service by himself.
Cool, so what's the single line command needed to type in to start a
given package service?
Aren't sysrc(8) and service(8) for this kind of stuff?
They sure are.
Well, pkg install $service ; sysrc ${service}_enable=YES would do.
Although some services have different names than the packge, which is sort
of annoying.
Maybe service needs to be extended (seriously sysrc ${service}_enable=YES is
not user friendly) we have service -l that list the services, maybe a service
${service} on that create /etc/rc.conf.d/${service} with
${service}_enable=YES
in it and service ${service} off to remove it
maybe service -l could also be extended to show the current status (maybe
with a
-v switch)
but for sure having the service off by default is a good idea :)
Yeah, maybe having it populate an entry of service_enable=NO for now .
It's even more unclear-ish - it's not obvious which options control
services and which ones are configuration things. We don't call it
service_xxx_enable, right?
-a
___
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: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 01:57:52PM -0700, Adrian Chadd wrote:
On 17 July 2014 13:54, Baptiste Daroussin b...@freebsd.org wrote:
On Thu, Jul 17, 2014 at 10:21:17PM +0200, Andreas Nilsson wrote:
On Thu, Jul 17, 2014 at 10:15 PM, Navdeep Parhar npar...@gmail.com wrote:
On 07/17/14 13:12, Adrian Chadd wrote:
On 17 July 2014 13:03, Alberto Mijares amijar...@gmail.com wrote:
On Thu, Jul 17, 2014 at 2:58 PM, Adrian Chadd adr...@freebsd.org
wrote:
Hi!
3) The binary packages need to work out of the box
4) .. which means, when you do things like pkg install apache, it
can't just be installed and not be enabled, because that's a bit of a
problem;
No. Please NEVER do that! The user must be able to edit the files and
start the service by himself.
Cool, so what's the single line command needed to type in to start a
given package service?
Aren't sysrc(8) and service(8) for this kind of stuff?
They sure are.
Well, pkg install $service ; sysrc ${service}_enable=YES would do.
Although some services have different names than the packge, which is sort
of annoying.
Maybe service needs to be extended (seriously sysrc ${service}_enable=YES
is
not user friendly) we have service -l that list the services, maybe a
service
${service} on that create /etc/rc.conf.d/${service} with
${service}_enable=YES
in it and service ${service} off to remove it
maybe service -l could also be extended to show the current status (maybe
with a
-v switch)
but for sure having the service off by default is a good idea :)
Yeah, maybe having it populate an entry of service_enable=NO for now .
then you need to extend rcng to support /usr/local/etc/rc.conf.d so the packages
can install them without touching base :) and we will need to wait for all
supported FreeBSD version to have the said modification)
It's even more unclear-ish - it's not obvious which options control
services and which ones are configuration things. We don't call it
service_xxx_enable, right?
imho this is obvious xxx_enable == control service.
regards,
Bapt
pgp3MU6Pix1ZM.pgp
Description: PGP signature
Re: HOWTO articles for migrating from Linux to FreeBSD, especially for pkg?
On Thu, Jul 17, 2014 at 09:57:44PM +0200, Andreas Nilsson wrote: On Thu, Jul 17, 2014 at 9:28 PM, Adrian Chadd adr...@freebsd.org wrote: Hi! 3) The binary packages need to work out of the box 4) .. which means, when you do things like pkg install apache, it can't just be installed and not be enabled, because that's a bit of a problem; I disagree on this. For network services on linux ( apart from ssh ), I want that started very seldom. But I do want the package installed so that when I need it, it is there. Having it autostart as part of being installed is breaking KISS and in some way unix philosophy: I asked for something to be installed, not installed and autostarted. 5) .. and then we need examples of actually deploying useful scenarios, like so here's what you type to get django working right, here's how you get a default memcached that works well, here's how you bring up node.js, etc. Oh yes. I think that quite a few packages have default options that make them unsuitable for out-of-box usage, ie some lack the sane default dbi-stuff and so on. Reporting them is very much needed, we try to change this but without report it is hard, as much as I can I use vanilla packages now, and I discovered that they are now pretty much sane, a few example has been found and modified recently like nginx not supporting https by default, so do not hesitate to report any unsuitable options for out-of-box usage. regards, Bapt pgpXV_Hvpzx3a.pgp Description: PGP signature
[QAT] 361977: 4x leftovers, 1x ???, 51x success
Add DOCS to OPTIONS_DEFINE to ports that check for PORT_OPTIONS:MDOCS. - Build ID: 20140715165800-27023 Job owner: ad...@freebsd.org Buildtime: 2 days Enddate: Fri, 18 Jul 2014 00:40:09 GMT Revision: 361977 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=361977 - Port:security/amavis-stats 0.1.12_3 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377550/amavis-stats-0.1.12_3.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377551/amavis-stats-0.1.12_3.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377552/amavis-stats-0.1.12_3.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377553/amavis-stats-0.1.12_3.log - Port:security/apg 2.3.0b_2 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377554/apg-2.3.0b_2.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377555/apg-2.3.0b_2.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377556/apg-2.3.0b_2.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377557/apg-2.3.0b_2.log - Port:security/botan110 1.10.7 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377558/botan110-1.10.7.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377559/botan110-1.10.7.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377560/botan110-1.10.7.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377561/botan110-1.10.7.log - Port:security/courier-authlib 0.66.1 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377562/courier-authlib-0.66.1.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377563/courier-authlib-0.66.1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377564/courier-authlib-0.66.1.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377565/courier-authlib-0.66.1.log - Port:security/gnutls 2.12.23_6 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377566/gnutls-2.12.23_6.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377567/gnutls-2.12.23_6.log Buildgroup: 9.2-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377568/gnutls-2.12.23_6.log Buildgroup: 9.2-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377569/gnutls-2.12.23_6.log - Port:security/libgcrypt 1.5.3_3 Buildgroup: 8.4-QAT/amd64 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377570/libgcrypt-1.5.3_3.log Buildgroup: 8.4-QAT/i386 Buildstatus: SUCCESS Log: https://qat.redports.org//~ad...@freebsd.org/20140715165800-27023-377571/libgcrypt-1.5.3_3.log Buildgroup: 9.2-QAT/amd64 Buildstatus:
