Date: Wed, 6 Aug 2014 23:07:59 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Melvyn Sopacua <melvyn@magemana.nl> Cc: ports@FreeBSD.org Subject: Re: How to tell pkg it's OK to overwrite files by another port Message-ID: <20140806210759.GQ17537@ivaldir.etoilebsd.net> In-Reply-To: <alpine.BSF.2.00.1408062112220.72407@fire.magemana.nl> References: <alpine.BSF.2.00.1408050528170.52235@fire.magemana.nl> <20140805143415.GD17537@ivaldir.etoilebsd.net> <alpine.BSF.2.00.1408062112220.72407@fire.magemana.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--eBTWNsZZiigckDWV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 06, 2014 at 09:19:48PM +0200, Melvyn Sopacua wrote: > Hi Baptiste, >=20 > On Tue, 5 Aug 2014, Baptiste Daroussin wrote: >=20 > > On Tue, Aug 05, 2014 at 05:35:03AM +0200, Melvyn Sopacua wrote: > >> Hi, > >> > >> the issue: > >> for www/magento there is a sample data package. I'd like to make a port > >> for it, but the sample data overwrites a few files in the www/magento > >> port's installed files to match the sample theme. > >> > >> This is OK and needed. But I don't know how to tell pkg this. > >> > >> I can make the sample data an option in the magento port and keep it in > >> one port, but this would put a large burdon on maintaining the pkg-pli= st > >> on upgrades as sample-data is only updated when backwards incompatible > >> changes are made to the core that make the older sample data unusable. > >> So I prefer to maintain it as a separate port. > >> > > There is a problem if that is how the port works. If magento expect som= e data to > > be replaced changed etc then it should not be tracked by the package to= avoid an > > upgrade of the package to overwrite the user special version which is w= hy pkg(8) > > has a strong hold on which files belongs to which package. > > > > So I think magento should be fixed in that regard. otherwise there is t= he > > PERMISSIVE options for pkg(8) but this is really really not recommanded= to use. > > The best is again to fix the magento port so it allows the normal use c= ases. >=20 > It's going to be a hack either way. > Think of it as two sample files from different sources: > default.conf.sample > optimized.conf.sample >=20 > Both are candidates for myconfig.conf, where optimized should win and > otherwise default, but they come from two different ports. This may > actually be the way to handle it, if @sample didn't assume the same > basename. >=20 > So I guess I have to install two different .sample files and a > pkg-(de)install script that updates to the right one, keeping the actual > file out of the pkg-plist. >=20 > That's the least hack-ish I can come up with for now, but I'm open to > suggestions. >=20 > -- > Melvyn There is the @sample keyword for that ;) regards, Bapt --eBTWNsZZiigckDWV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlPimS8ACgkQ8kTtMUmk6EwsdACZAb5LctG4oeHtZxKhpt8IWah2 6fEAoKQIFyrxTcm7/E2di6BmnxjUJe/Z =art1 -----END PGP SIGNATURE----- --eBTWNsZZiigckDWV--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140806210759.GQ17537>