From owner-freebsd-stable@FreeBSD.ORG Sun Jun 10 17:20:54 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0E928106566B; Sun, 10 Jun 2012 17:20:54 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 27F9E8FC1E; Sun, 10 Jun 2012 17:20:52 +0000 (UTC) Received: by bkvi18 with SMTP id i18so3670786bkv.13 for ; Sun, 10 Jun 2012 10:20:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=CWKp+/IMMY7GdfzqEE6IbgsblAgQDomGW2rElGu+RTQ=; b=Wjvag34+nlQ7oRPnHYrTUXRknk9xp1Uj+pN9eVNRXJKAr7LQbnL09kMrgsLnjBC2LA PdXK7a2JGbtAORLxvwTt++V9MZKCrtqNGvCX0FhjPIuVLGIXr1BMzLedUlMTBrF/nWXu 7I4tNIeoGZ3ownkXoZir8umIoGQ+LNrfxnDkVGeq0Xz7+dUzdDzN0xIsEGnwwtugVsSI LMkHk10sw2Zh6Z3biQxQfOxLD7ARNUUkT5zatBW2tXrlvDMG5hTmGPQgxVRgifrr1cs3 6PLPlIi303iPsZCgl4OF8cYVuNhP0T3yDh4AQRAYKUzLyndPHxPBpJSLlU4afdm7i0c8 3hUw== Received: by 10.204.154.214 with SMTP id p22mr8877374bkw.115.1339348851854; Sun, 10 Jun 2012 10:20:51 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.204.171.138 with HTTP; Sun, 10 Jun 2012 10:20:21 -0700 (PDT) In-Reply-To: <4FD4D4F6.9090805@zedat.fu-berlin.de> References: <20120604110339.GA9426@equilibrium.bsdes.net> <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> <20120610165455.1c59e8ae@zelda.sugioarto.com> <4FD4C0AC.4000802@yahoo.com> <4FD4D4F6.9090805@zedat.fu-berlin.de> From: Chris Rees Date: Sun, 10 Jun 2012 18:20:21 +0100 X-Google-Sender-Auth: 0-bF1tgGB35-dG1TY4rvshiiM-4 Message-ID: To: "O. Hartmann" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Current FreeBSD , freebsd-stable@freebsd.org, Ports FreeBSD Subject: Re: WAS: Re: Why Are You NOT Using FreeBSD ? New: port annoyance LibreOffice X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jun 2012 17:20:54 -0000 On 10 June 2012 18:10, O. Hartmann wrote: > 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: >>> >>>> Er... people always test their commits. =A0Sometimes 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 ports >>> 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 >>> >>> ----------------------------------------------------------------------- >>> =A0 =A0 =A0 =A0 =A0Oh dear - something failed during the build - sorry = ! >>> =A0 =A0For more help with debugging build errors, please see the sectio= n in: >>> =A0 =A0 =A0 =A0 =A0 =A0 =A0http://wiki.documentfoundation.org/Developme= nt >>> >>> =A0 =A0internal build errors: >>> >>> ERROR: error 65280 occurred while >>> making >>> /usr/workdir-ports/usr/ports/editors/libreoffice/work/libreoffice-core-= 3.5.2.2/vcl/prj >>> >>> >>> =A0 it seems that the error is inside 'vcl', please re-run build >>> =A0 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 >>> =A0 =A0updating the modules that belong to these ports. I've seen 100x = the >>> =A0 =A0same message that p5-XML-Parser does not work and know what it m= eans, >>> =A0 =A0but this should be resolved by the port system. I mean, when you >>> =A0 =A0update perl, the perl modules won't work anymore. This is totall= y >>> =A0 =A0clear 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. There's an UPDATING message written for that very purpose. >>> >>> - When specifying WITHOUT_X11 the ports should respect this and not try >>> =A0 =A0to pull in the X11 variants of ports. I regularly see some ports >>> =A0 =A0pulling ImageMagick instead of the already installed >>> =A0 =A0ImageMagick-nox11. I still do not fully understand what is going= on >>> =A0 =A0with WITHOUT_GNOME, but I'll try to figure it out later. But I a= m >>> =A0 =A0quite sure that some ports pull in unneeded Gnome dependencies. >>> >>> - Ports are being marked as interactive and stop the update process. Th= e >>> =A0 =A0idea behind portmaster was (earlier) to avoid interactive buildi= ng of >>> =A0 =A0ports and ask all the needed questions, before the builds start.= I >>> =A0 =A0mean, earlier, I could get out and enjoy some coffee outdoors, n= ow I >>> =A0 =A0have 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. FORCE_PKG_REGISTER. >>> >>> - It would be nice to have a mechanism that tells you that your perl, >>> =A0 =A0mysql or whatever is not the default version anymore and you sho= uld >>> =A0 =A0consider updating to the default (and recommended) port. >>> >>> >>> Martin >> >> From /etc/defaults/periodic.conf: >> >> # 400.status-pkg >> weekly_status_pkg_enable=3D"YES" =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# Find o= ut-of-date pkgs >> pkg_version=3Dpkg_version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 # Use this program >> pkg_version_index=3D/usr/ports/INDEX-9 =A0 =A0 =A0# Use this index file >> >> There's an override script in ports-mgmt/portupgrade that uses it's >> database, also. >> >