gstreamer* ports all have the same UNIQUENAME and OPTIONSFILE ??

Alfred Bartsch bartsch at
Wed Jul 4 07:50:08 UTC 2012

Hash: SHA1

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 
> 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, so I consider it best moving "distfiles" to /var/db/pkg.
Then there would be no more messages like "directory not empty" while
executing "make rmconfig" in a port directory and perhaps portmaster
would no longer remove stale distfiles which aren't really stale but
from different installed program versions with similar names.
- -- 
Alfred Bartsch
Data-Service GmbH
Version: GnuPG v1.4.11 (FreeBSD)
Comment: Using GnuPG with Mozilla -


More information about the freebsd-multimedia mailing list