Date: Sun, 10 Jun 2012 19:10:14 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Ports FreeBSD <freebsd-ports@freebsd.org> Cc: Current FreeBSD <freebsd-current@FreeBSD.org>, freebsd-stable@freebsd.org Subject: WAS: Re: Why Are You NOT Using FreeBSD ? New: port annoyance LibreOffice Message-ID: <4FD4D4F6.9090805@zedat.fu-berlin.de> In-Reply-To: <4FD4C0AC.4000802@yahoo.com> References: <CAOgwaMvsv3e1TxDauV038Pp7LRiYeH7oAODE%2Bw-pxHt9oGrXMA@mail.gmail.com> <20120604110339.GA9426@equilibrium.bsdes.net> <CAOjkAUe0_U==vjQGO77sQy=4JJ_e_ypoGpVbf1Mg62ttXATJYw@mail.gmail.com> <4FD2D4CC.3080109@ateamsystems.com> <4FD3003C.4080109@zedat.fu-berlin.de> <4FD352FF.9090101@ateamsystems.com> <4FD357F2.9090901@zedat.fu-berlin.de> <4FD35905.9080500@ateamsystems.com> <20120610121210.3ce1bd9d@zelda.sugioarto.com> <CADLo838gS7L=Sy9Giow1gYMtM2n4NnoHJWm8p3ZCvi6CZbMWhg@mail.gmail.com> <20120610165455.1c59e8ae@zelda.sugioarto.com> <4FD4C0AC.4000802@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCC49ECD2589BC8743D2423B4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 06/10/12 17:43, John Merryweather Cooper wrote: > On 06/10/12 09:54, Martin Sugioarto wrote: >> Am Sun, 10 Jun 2012 11:37:09 +0100 >> schrieb Chris Rees<crees@FreeBSD.org>: >> >>> Er... people always test their commits. Sometimes edge cases will >>> creep in, such as the libreoffice failure which was due to different >>> configurations, but to suggest that the commit wasn't tested is quite= >>> frankly insulting-- it built on a clean system perfectly well. >> Hi, >> >> I don't mean to insult anyone. As I have already told, I am really >> thankful that people invest their precious time into updating the port= s >> collection. >> >> Whatever "clean system" means. It is surely not the default case that >> someone has got a freshly installed set of ports. >> >> Among all the default problems with ports, libreoffice[1] adds to the >> group of annoyances[2] at the moment. I don't know when I have seen >> "portmaster -ad" run through successfully last time. I need more and >> more "-x" options to exclude ports which fail to build. >> >> [1] german/libreoffice and libreoffice fails all the time in >> (LOCALIZED_LANG is set to "de"): >> >> Module 'lingucomponent' delivered successfully. 12 files copied, 2 >> files unchanged >> >> ----------------------------------------------------------------------= - >> Oh dear - something failed during the build - sorry ! >> For more help with debugging build errors, please see the section i= n: >> http://wiki.documentfoundation.org/Development >> >> internal build errors: >> >> ERROR: error 65280 occurred while >> making >> /usr/workdir-ports/usr/ports/editors/libreoffice/work/libreoffice-core= -3.5.2.2/vcl/prj >> >> >> it seems that the error is inside 'vcl', please re-run build >> inside this module to isolate the error and/or test your fix: >> ----------------------------------------------------------------------= - >> >> >> Whatever this tries to tell me. I don't get it. This is a completely >> useless error message for me. Not even in german/libreoffice. i try to build the standard version and I receive the same error. I can fix this by doing what the buildsystem suggests, but then I have a stop in sfx2 and others and it ends up in some module called tail_XXXX, where the build never ends when performing the repair as suggested. I had once a box running all the night looping building in this folder. >> >> [2] The default annoyances are for example: >> >> - After updating perl, php or whatever, it makes sense to enforce >> updating the modules that belong to these ports. I've seen 100x the= >> same message that p5-XML-Parser does not work and know what it mean= s, >> but this should be resolved by the port system. I mean, when you >> update perl, the perl modules won't work anymore. This is totally >> clear and it makes sense to update them first before going on. I can confirm that. I fixed that for me by "portmaster p5-" in case p5-SAX-XXX failed. >> >> - When specifying WITHOUT_X11 the ports should respect this and not tr= y >> to pull in the X11 variants of ports. I regularly see some ports >> pulling ImageMagick instead of the already installed >> ImageMagick-nox11. I still do not fully understand what is going on= >> with WITHOUT_GNOME, but I'll try to figure it out later. But I am >> quite sure that some ports pull in unneeded Gnome dependencies. >> >> - Ports are being marked as interactive and stop the update process. T= he >> idea behind portmaster was (earlier) to avoid interactive building = of >> ports and ask all the needed questions, before the builds start. I >> mean, earlier, I could get out and enjoy some coffee outdoors, now = I >> have to sit at the keyboard. This is unacceptable! ;) "portmaster" does even more damage. Sometimed a port reels in some newly updates, a port gets deleted. if on of the to be updated prerquisits fail, the port in question isn't there anymore. "portmaster" fails quite often in "oberwriting" remnant files. If a port gets corrupted by accident, like graphics/netpbm, One need to delete all binaries manually from /usr/local/bin, otherwise the installation fails. Somehow I wish to have a "brute force" knob to overwrite everything in a brutal way. >> >> - It would be nice to have a mechanism that tells you that your perl, >> mysql or whatever is not the default version anymore and you should= >> consider updating to the default (and recommended) port. >> >> >> Martin >=20 > From /etc/defaults/periodic.conf: >=20 > # 400.status-pkg > weekly_status_pkg_enable=3D"YES" # Find out-of-date pkgs= > pkg_version=3Dpkg_version # Use this program > pkg_version_index=3D/usr/ports/INDEX-9 # Use this index file >=20 > There's an override script in ports-mgmt/portupgrade that uses it's > database, also. >=20 --------------enigCC49ECD2589BC8743D2423B4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJP1NT9AAoJEOgBcD7A/5N8wPgIAN490p9vbsOW6VeCymRZJ7HZ S56xKvXT6b3Fpc62968OdF2Z9Aybsb3vgdKJq2xKRwkkTavlb/sRD+azPrR5udbU Y+zrFDdPeNAL+MBQR4KZY7ply4gfNKr5fs6Z/QQLm8iIdVqqNXW1rEjMSIJCvN+L aVFLQc6PH+ikhco6c+PX1zvqV2mRDnDw8Mde6QJH7YLZagzdhIx5noCdLbQ3eFar 1no9MxJ08kB6az6dllbpJZF6eLpXGF1eR2nEXmCWixmCifGEn98qSB8GMPZ6zoW4 YYBx2VPUvrJsINkfOHN3/Fx2peqGcMyspHOMqeKat36a8vySQe21fYiUnw9c+o4= =5O0E -----END PGP SIGNATURE----- --------------enigCC49ECD2589BC8743D2423B4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FD4D4F6.9090805>