Date: Fri, 15 Aug 2014 13:43:25 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: =?UTF-8?Q?=C5=81ukasz_W=C4=85sikowski?= <lukasz@wasikowski.net>, freebsd-ports@freebsd.org Subject: Re: Ports, pkg's confusion on upgrades... Message-ID: <2A69DCE1B30998B865D46192@Mail-PC.tdx.co.uk> In-Reply-To: <53EDE679.9050105@wasikowski.net> References: <52652ABEC925BB93CB8877CD@Mail-PC.tdx.co.uk> <53EDE679.9050105@wasikowski.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--On 15 August 2014 12:52 +0200 =C5=81ukasz W=C4=85sikowski = <lukasz@wasikowski.net>=20 wrote: > You could solve this by using your own poudriere - create repos with > your own port's options and pkg upgrade everything. Your current > approach - mixing packages and ports - is not supported IIRC. Thanks for the suggestion - and I take your point about not mixing ports &=20 packages... Setting up our own pkg repo though sounds like a lot of work (all for the=20 sake of about probably 2 packages we need to change the options on) - I'd=20 guess there's no way of telling pkg to use 'our' repo for these 2-3=20 packages, and the main one for everything else? I suppose the other option is just ignore packages, and stick to ports?=20 (presuming ports will always be around :) I'd also still like to know if there's a way of getting 'pkg upgrade' to=20 spit out why it wants to install a 'new package' - when none of the current = packages have a dependency on it? This is going to happen at some point, even on a pkg only system (e.g. what = happens when pkg upgrade says it's going to install X11 [which nothing=20 currently 'depends' on] - but obviously some upgraded package does - you'd=20 really want to know what's going to cause X to be installed? -Karl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2A69DCE1B30998B865D46192>