6100 subdirectories in /usr/ports/devel!
blubee blubeeme
gurenchan at gmail.com
Mon Feb 19 14:13:04 UTC 2018
On Mon, Feb 19, 2018 at 7:56 PM, Gleb Popov <6yearold at gmail.com> wrote:
> On Mon, Feb 19, 2018 at 9:45 AM, Julian Elischer <julian at freebsd.org>
> wrote:
>
> > On 29/12/17 5:16 am, Bob Willcox wrote:
> >
> >> On Fri, Dec 29, 2017 at 03:54:28AM +0700, Eugene Grosbein wrote:
> >>
> >>> 29.12.2017 3:36, Bob Willcox wrote:
> >>>
> >>> Does anyone else feel that having 6100 subdirectories (939 are for py-*
> >>>>> stuff)
> >>>>> is a bit excessive?
> >>>>>
> >>>> It is. But py-* stuff has second place only:
> >>>>
> >>>> $ ls /usr/ports/devel | sed 's/-.*//' | sort | uniq -c | sort -rn |
> head
> >>>> 1908 p5
> >>>> 964 py
> >>>> 600 rubygem
> >>>> 280 hs
> >>>> 176 pear
> >>>> 57 R
> >>>> 56 pecl
> >>>> 48 elixir
> >>>> 47 geany
> >>>> 43 erlang
> >>>>
> >>> In fact, ports/devel is first but not only category having similar
> >>> problem with p5-* stuff:
> >>>
> >>> $ cd /usr/ports
> >>> $ find . -type d -mindepth 1 -maxdepth 1 | while read category; do
> >>> printf "%15s " ${category#./}; ls $category | sed 's/-.*//' | sort |
> uniq
> >>> -c | sort -rn | head -1; done | sort -k 2,2 -rn | head -15
> >>> devel 1908 p5
> >>> www 807 p5
> >>> textproc 617 p5
> >>> net 327 p5
> >>> databases 259 p5
> >>> security 258 p5
> >>> math 146 p5
> >>> mail 145 p5
> >>> graphics 100 p5
> >>> editors 98 libreoffice
> >>> sysutils 75 rubygem
> >>> converters 72 p5
> >>> misc 63 p5
> >>> net-mgmt 56 p5
> >>> x11-toolkits 49 p5
> >>>
> >>> Yeah, I happened to notice the py-* stuff due to some problems I have
> >> been
> >> having with synth. I did notice the large number of p5-* subdirs but
> >> didn't
> >> count them. :)
> >>
> >> Certainly seems to be out of control...
> >>
> >> the py and p5 stuff is a symptom of another problem, which is that we
> are
> > only second level for those files...
> >
> > the correct behaviour in my point of view is for our packages/ports
> system
> > to delegate to pypi or similar for python and to CPAN for perl.
>
I agree with this as well, why maintain these ports when they're being
maintained upstream. Plus, if we do need patches, they can be applied
during the build step.
> >
> > maybe with the ability to add some patches on the way through.. There is
> > just too much going on there for us to follow properly.
>
>
> I double this thought! This is what I'm goinf to head to with Haskell ports
> one time.
>
> There is a hitch, though. Hackage, the haskell package database, is a dump.
> You easily can get a version clash between to packages. No one curates
> them. So, while there was only Hackage maintaining hs- ports made sense -
> we've been cheking all the packages we have to compile/work together. But
> now Stackage emerged, which is a curated package DB, so our ports is a
> duplicated work now. The port is only needed if it is not present on
> Stackage or if it require FreeBSD specific patches that haven't been
> upstreamed yet.
>
> If PyPi and CPAN has the same notion of curated package set, we should not
> duplicate this effort and remove much of our py- and p5- ports.
>
>
> >
> >
> > _______________________________________________
> > freebsd-ports at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
> >
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>
More information about the freebsd-ports
mailing list