Date: Mon, 04 Apr 2016 09:45:51 +0300 From: abi@abinet.ru To: freebsd-ports@freebsd.org Subject: Re: gentoo's package.provided equivalent? Message-ID: <979c97dea4c547a91f117b52f6db4dfc@abinet.ru> In-Reply-To: <4b65ec30864d548eaa7efde0c3dd01cf.squirrel@mail.kazanfieldhockey.ru> References: <4b65ec30864d548eaa7efde0c3dd01cf.squirrel@mail.kazanfieldhockey.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
If library in port tree you can fetch old version of the port from svn manually or with portdowngrade. anatoly@kazanfieldhockey.ru писал 2016-04-03 04:54: > Sometimes i need to build specific version of some library from source, > not from ports. How can I tell port system about it. There was no problem > with old pkg_, because I was able just to put dummy directory into > /var/db/pkg and port system knows it is installed (although maybe that was > ugly hack). But what I can do with pkgng now? For example, Gentoo linux > has /etc/portage/profile/package.provided file for such a situation. Is > there some equivalent? > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-ports@freebsd.org Mon Apr 4 07:34:38 2016 Return-Path: <owner-freebsd-ports@freebsd.org> Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9BB0B02A78 for <freebsd-ports@mailman.ysv.freebsd.org>; Mon, 4 Apr 2016 07:34:38 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from toco-domains.de (mail.toco-domains.de [176.9.39.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B3FEF16C0 for <freebsd-ports@freebsd.org>; Mon, 4 Apr 2016 07:34:38 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 74D721AAF060; Mon, 4 Apr 2016 09:34:30 +0200 (CEST) Subject: Re: synth just deleted 290 ports on my machine on second try ;) To: Kevin Oberman <rkoberman@gmail.com> References: <1459448404.36265.19.camel@mathiaspicker.net> <56FE58E3.2020803@toco-domains.de> <CAN6yY1uT+dYNd7+zUUxiRKyqB7c6U0mTXV4Vf6AC1gXF0s=WFg@mail.gmail.com> Cc: FreeBSD Ports ML <freebsd-ports@freebsd.org> From: Torsten Zuehlsdorff <mailinglists@toco-domains.de> Message-ID: <57021906.9020706@toco-domains.de> Date: Mon, 4 Apr 2016 09:34:30 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <CAN6yY1uT+dYNd7+zUUxiRKyqB7c6U0mTXV4Vf6AC1gXF0s=WFg@mail.gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>; List-Post: <mailto:freebsd-ports@freebsd.org> List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>, <mailto:freebsd-ports-request@freebsd.org?subject=subscribe> X-List-Received-Date: Mon, 04 Apr 2016 07:34:39 -0000 On 02.04.2016 08:17, Kevin Oberman wrote: > On Fri, Apr 1, 2016 at 4:17 AM, Torsten Zuehlsdorff < > mailinglists@toco-domains.de> wrote: > >> On 31.03.2016 20:20, Mathias Picker wrote: >> >> What can I do now, other than using portmaster to rebuild all ports? >>> >> >> You can use poudriere to rebuild all the ports and use its local >> repository for pkg. >> >> Greetings, >> Torsten > > > But that's the whole point of synth. It exists to allow you to build > packages for customized ports without the heavier weight of poudriere. That is true. But that is the answer because you would not build everything from the portstree. This is quite easy. synth failed. Next option is poudriere. The other option is to contact marino@ and report the issue and wait for the fix. Till then you could not use your machines. My answer gives you back a working machine, the possibility to report the issue and wait for the issue. And at least switch back to synth again. :) Greetings, Torsten
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?979c97dea4c547a91f117b52f6db4dfc>