Re: net/boinc-client: make LINUX option a default or Slave port?
Hello, On Wed, Jan 18, 2017 at 5:10 PM, Larry Rosenman wrote: > > I'm working on making Manfred's sources used in the port, and will *NOT* > be flipping the LINUX option. I'll be pushing an update for > net/boinc-client > soon. > FWIW, the latest boinc-client in the ports tree installed without problems and works with boinc_curses root@kg-vm# pv boinc* [Reading data from pkg(8) ... - 59 packages found - done] boinc-client-7.2.33_7 = up-to-date with port boinc_curses-0.2.2_1= up-to-date with port on root@kg-vm# uname -a FreeBSD kg-vm.kg4.no 10.3-STABLE FreeBSD 10.3-STABLE #0 r311695: Sun Jan 8 20:58:02 CET 2017 r...@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64 I haven't verified that it actually works yet (setiathome is down for maintenance, and I haven't compiled the binaries yet) as I don't have any project binaries for FreeBSD right now. (I tried binaries for Milkyway that I had laying around, but I'm not sure they actually work on FreeBSD 10.3) -- Regards, Torfinn Ingolfsen ___ 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: ports and dependency hell
On 07/02/2017 18:03, Julian Elischer wrote: This is a serious post on a serious issue that ports framework people seem unaware of. (...) The call "It just works under linux, select the versions you want of each package and type make" is often heard around the company. And management is not totally deaf. Hi Julian, I may not fully understand how it works but what prevents you from getting sources for the version you want and typing make in them, exactly the way you do it in Linux? It should pick up the versions of dependencies currently installed in the system and compile for them. Is it only when you want to use the ports infrastructure that poses a problem? Grzegorz ___ 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: How to see package dependencies (scponly depends on ccache?)
On 06/02/2017 09:37, Matthias Fechner wrote: > Am 05.02.2017 um 14:23 schrieb tech-lists: >> does your /etc/make.conf have a reference to ccache ? > > /etc/make.conf is empty, only my poudiere make.conf holds the following: > DEFAULT_VERSIONS=php=5.6 apache=2.4 mysql=10.1m bdb=6 ssl=openssl > WITH_BDB6_PERMITTED=1 > WITH_OPENSSL_PORT=yes > WANT_OPENLDAP_SASL=yes > > WITH_MPM=event > OPTIONS_UNSET=DEBUG DOCBOOK EXAMPLES > OPTIONS_SET=proxy dav ssl ldap > > DISABLE_LICENSES=yes > > All packages (build with poudiere on another machine) are installed > using pkg. Does the Makefile for scponly contain any ccache reference? Because if not, I'm stumped! -- J. ___ 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"
ports and dependency hell
This is a serious post on a serious issue that ports framework people seem unaware of. It' getting too easy to get into dependency hell here (I've spent the last week fighting this) In a production system we have to choose packages from different eras. This is because on an average product different teams are responsible for different parts of the product, and they all have their own requirements. Not to mention the stuff that comes in from third party vendors which "must use version X of bar and Version Z of foo". This is something that is a fact of life in commercial vendors. Ports needs to support it, and fast because currently ports is a reason to switch to Linux. (ammunition for the Linux fanboys). We are only staying for the ZFS support but that reason will evaporate soon. We may need node.js 6.95 and a particular version of an apache mod for example, and a specific version off npm, which all only appeared in the ports tree at different times, so either we completely ditch the ports tree all together and import buildroot2 , which allows every package to have its own revision (but is Linux centric), or we need to generate frankenports trees. My curent iteration has 359 different packages, so you an imagine the hilarity if I need to slide 20 of those back or forth, all independently. There doesn't seem to be any understanding of this fact from the ports framework, and it means one has to keep one's own ports tree in source control, as a branch off the FreeBSD one. (maybe I should look at pkgsrc).. the problem is that the internal APIs of ports are changing too much. If you are going to change the API, then you need to be able to declare the version separately, maybe in a version/distinfo file that can be pulled in separately at a different rev, rather than having it built into the main Makefile of each port. Maybe the Makefile specifies a revision range it can be used with, but that would make a huge improvement right there. You can not just slide one port up by 3 months, and another down by 3 months to get the revs one needs because the damned Mk files have changed. If I coudl leave the bulk of the Makefile alone and just slide the 'distingo/rev' file, (or be able to select a rev from one htat gives many alternatives, that woudl be "wonderful". Please, ports framework people, think about how this can be done, If I have to edit a file, the game is lost. Can we please get some understanding from ports people that they are making things REALLY HARD on vendors and it really strengthens the hands of the "ditch FreeBSD and go to Linux" crowd when I need to spend a whole week trying to integrate in a set of 5 new ports into the product. The call "It just works under linux, select the versions you want of each package and type make" is often heard around the company. And management is not totally deaf. If you want to see how its' done better (still not perfect), go build a busybox system. you can effectively select any version of any tool and they all communicate via the pkgconf mechanism and you get the result you want.(mostly). And the API is stable. On the pkg side of things we need the ability for pkg to say "yeah I know I'm looking for foo-1.2.3.txz as a perfect match, but I've been given some slack on the third digit and I can see a foo-1.2.1.txz, so I'll install that instead". Otherwise we just have to spend WAY too much time generating dozens of "matching sets" of packages , that must be kept around forever if just one machine shipped with that set, not to mention the fact that making the matching set is often a real task. The way to get around the problem above CAN be (not always) to install foo.1.2.1 first and THEN install the package you actually want, and pkg will accept it. The problem comes when pkg needs to install a dependency itself. Then it becomes "super picky", when there is actually a range of package revisions that would do. Instead of letting pkg install what it needs, we need to manually set up scripts to install the dependencies. so that all the work done by pkg is wasted. Please think about these two issues.. Julian ___ 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 (deskutils/when)
## Walter Schwarzenfeld (w.schwarzenf...@utanet.at): > It works if I remove the /usr/bin/perl link. > (But I have to change all shebangs in the perlscripts ... it will be > simpler with the link). The "/usr/bin/perl" hasn't been part of ther perl packages for quite some time - packages can't rely on it being present. But that's why w ehave USES+=shebangfix - it will fix all your shebangs for you (if used correctly). Regards, Christoph -- Spare Space ___ 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 (deskutils/when)
It works if I remove the /usr/bin/perl link. (But I have to change all shebangs in the perlscripts ... it will be simpler with the link). ___ 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"
shebangfix (deskutils/when)
I have a link in /usr/bin to /usr/local/bin/perl and set DEVELLOPER)yes. Only with DEVELOPER=yes, stage-qa states (port desktils/when and only with DEVELOPER=yes). Error: '/usr/bin/perl' is an invalid shebang you need USES=shebangfix for 'bin/when' *** Error code 1 ___ 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: 12-CURRENT won't configure to download packagesite.txz yet
On 02/ 6/17 09:59 PM, Allan Jude wrote:
On February 7, 2017 2:35:16 AM GMT+01:00, Jeffrey Bouquet
wrote:
All the files
/etc/FreeBSD.conf
/usr/local/etc/pkg/repos/FreeBSD.conf
/usr/local/etc/pkg.conf
I edit time after time for
{$ABI} which gives FreeBSD:11:i386 but I am on 12-CURRENT i386
Anytime I try to attune to
freebsd:12:x86:32or
FreeBSD:12:i386 ...
it downloads the packagesite again, as it does in the ABI example, but
a terse
error of wrong architecture, etc, and a fail to do anything to upgrade
to Pkg-12.
Can the proper file be rename upstream to what its architecture in
simpler terms:
like packagesite-i386-12.txz and a message printed upon de-TXZ the file
so that
the proper nomenclature is given to put into each of those three files
above
so that the generic packagesite.txz will not error out upon download?
Or, put the instructions in /usr/src/UPDATING ?? since it is part of
base?
Or some other way to de-showstopper this v11 April 2016 CURRENT to v12
Feb 2017 CURRENT
upgrade which still has failed to enable seamonkey-2.46_5 to run
non-segfault [ ie cannot run ]
vs seamonkey-2.46_4 which four days ago ran without EVER segfaulting??
And cannot build
>from ports for obscure .h clang-header file related reasons?
___
freebsd-curr...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
"freebsd-current-unsubscr...@freebsd.org"
Please provide the output of:
uname -a
machine on which firefox, thunderbird, seamonkey, cc, pkg work:
...
11.0-CURRENT #2
R298350
Wed Apr 20 2016
I386
1100105
1100105
DEC22KRNL10 ( not GENERIC )
...
machine on which firefox has broken numeric input [ I cannot log into
the FreeBSD forum as my nickname has a "2" within it...
nor use browser search in firefox that searches for terms with
a "2" within the text field... jumps to another tab..., cc MAY be fixed,
pkg still works only at v11,
seamonkey segfaults, thunderbird segfaults, otter-browser has bus
error, seamonkey won't build
due to maybe clang header files:
..
12.0-CURRENT #3
R313305
Mon Feb 6 2017
i386
1200020 ( guess from strings on the kernel) ... (forgot to run uname
when booted into the system)
1200020 ( guess from strings on the kernel) "
DEC22KRNL10 (not GENERIC)
and per pkg -vv, still v11...
uname -K
uname -U
Again, maybe a ${ABI} set of three files (FreeBSD.conf (2) , pkg.conf )
that I could use as a template
may fix the package issue and if that is fixed, could fix the
seamonkey/thunderbird/firefox issues...
Precise documentation is lacking in the limited time I have to test
solutions in forum and mailing
list posts.
.
___
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"
