Re: gem, pip et al vs. pkg

On 08.06.2016 02:53, Kurt Jaeger wrote: Hi! The ports tree has thousands of entries, which are simply thin wrappers around Ruby's gem or Perl's and/or Python's pip. Thanks again for asking the right questions. Please add go to that list 8-} Why do we need them? Obviously, it is primarily

Re: gem, pip et al vs. pkg

Hi! > The ports tree has thousands of entries, which are simply thin wrappers > around Ruby's gem or Perl's and/or Python's pip. Thanks again for asking the right questions. Please add go to that list 8-} > Why do we need them? Obviously, it is primarily > for other ports to be able to depend

gem, pip et al vs. pkg

The ports tree has thousands of entries, which are simply thin wrappers around Ruby's gem or Perl's and/or Python's pip. Most of these ports conWhy do we need them? Obviously, it is primarily for other ports to be able to depend on them. But why can't we satisfy this need without creating a