Date: Wed, 04 Jul 2012 01:06:21 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Alfred Bartsch <bartsch@dssgmbh.de> Cc: freebsd-multimedia@FreeBSD.org Subject: Re: gstreamer* ports all have the same UNIQUENAME and OPTIONSFILE ?? Message-ID: <4FF3F97D.1010905@FreeBSD.org> In-Reply-To: <4FF3F3BE.8040900@dssgmbh.de> References: <4FF383A8.4070809@FreeBSD.org> <4FF3F3BE.8040900@dssgmbh.de>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 07/04/2012 00:41, Alfred Bartsch wrote: > Am 04.07.2012 01:43, schrieb Doug Barton: >> Howdy, > >> Trying to track down a bug reported by a portmaster user I've >> noticed that all of the gstreamer* ports that I've checked so far >> all have the same UNIQUENAME, and thus, the same OPTIONSFILE. >> AFAICS gstreamer-plugins-all is the only port that sets OPTIONS, so >> in that sense it's not an issue. > >> However, portmaster uses UNIQUENAME to determine the location to >> store a file with the distfile info, and the fact that it's the >> same for every port is creating a conflict. See >> http://www.freebsd.org/cgi/query-pr.cgi?pr=106483 for more >> information about the concept. > >> This problem will theoretically go away if pkgng gets adopted, and >> I can fix it for portmaster by moving the distfile file into >> /var/db/pkg where I thought it should have been all along. But I >> thought I'd mention the UNIQUENAME issue in case it's something >> that y'all want to address. > >> Doug > > > Thank you for pointing this out. There are other ports with shared > UNIQUENAME, ... which is a bug, and needs to be fixed for pkgng purposes. > so I consider it best moving "distfiles" to /var/db/pkg. I'm in the process of working on that now. > Then there would be no more messages like "directory not empty" while > executing "make rmconfig" in a port directory That was fixed in bsd.port.mk recently. > and perhaps portmaster > would no longer remove stale distfiles which aren't really stale but > from different installed program versions with similar names. That's not related to this issue. portmaster does a pattern match on the distfiles, and does a pretty good job to not delete files that are valid for any installed port. This issue with the gstreamer* ports sharing UNIQUENAME has completely buggered that for 'portmaster -d' however. My goal for a long time has been to get the distfile info into the official db, and then relax the pattern matching in portmaster since we'll have a very good idea what the affected port is actually using. Unfortunately, portmgr has not shared my enthusiasm. Doug - -- This .signature sanitized for your protection -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJP8/l8AAoJEFzGhvEaGryE5zkIALuLtnHxfwbXfPEeBe1EVSZB 2b0Y40Eq+bioOHRTFAEx948Hwiqd44+ALCXG62j01zqgv+c185pH2VnIVRXFmBjG kk2Gjs3Oq97XA8ZKyigB+vaC4f4MM1/UAer9AOJRBauTnRDOt3gy3HE4drbP4qkx aIl7E1pHQAsTrHmEIOFhRaDfBzpvB1iUFg9mPTB7AdWiXkMtUU1m6n7rnHi0xXhT Ibyl/SuFMyZxQHZJKAFPvusSyZ+Sf1Jos/39mLJqikkQeYA25RjK8XKN9kpPOhwV pBK2KKF94FYoM2Lleah1o6JcBHMAyAj1Q7DpejU8h3TvgUHz0zC/VhtH+U3irsA= =hRKM -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FF3F97D.1010905>