Hi,
On Thu, May 19, 2016 at 12:45:48AM +0200, René J.V. Bertin wrote:
> On Wednesday May 18 2016 17:50:00 Brandon Allbery wrote:
>
> > The problem with this is that if a MacPorts user can't get something from a
> > prebuilt package, you have to force both the "user" and "developer" ports
> > to b
On Wednesday May 18 2016 17:50:00 Brandon Allbery wrote:
> The problem with this is that if a MacPorts user can't get something from a
> prebuilt package, you have to force both the "user" and "developer" ports
> to be installed because any dependents will necessarily be doing linking.
Yes, but i
On Wed, May 18, 2016 at 5:46 PM, René J.V. wrote:
> This got me thinking about more elegant ways to avoid the issue, in
> particular Debian/Ubuntu's approach of distinguishing "user" packages and
> "developer" packages. The former contain everything required to use the
> package, other than for d
Hi,
Time for one of my wild ideas :)
As some of you know, I've been working to make port:VLC independent of
port:ffmpeg so that the latter can be updated to a version that VLC will not
support for a while.
I went for an approach where port:VLC has an ffmpeg-VLC subport that builds and
install
