[oi-dev] oi-userland categories

Andreas Wacknitz A.Wacknitz at gmx.de
Thu Feb 18 16:14:00 UTC 2016


Am 18.02.16 um 10:30 schrieb Alexander Pyhalov:
> Hi.
>
> Today I wanted to add myspell dictionaries to oi-userland.
> As OI dictionaries are based on dictionaries from OpenOffice.org, 
> disappeared long ago, I wanted to base them on Debian dictionaries
> (which are created from well-known sources). But dictionaries are 13 
> packages (library/myspell/dictionary/*). I looked at oi-userland 
> components/ directory and it is a mess, I don't know where I can put 
> 13 more related packages. In userland style I'd create myspell 
> directory, creating individual components. But it's sill a mess.
>
> Let's look, currently we have the following "categories" - i.e. 
> directories under components, containing another components:
>
>         apache2-modules    - Apache 2.2 and 2.4 modules
>         aspell             - Aspell and its dictionaries
>         autoconf           - Different autoconf versions
>         automake           - Different automake versions
>         common-lisp        - common lisp libraries
>         docbook            - docbook stylesheets/dtds
>         e                  - Enlightenment
>         encumbered           - components which shouldn't appear in 
> main repository due to patent issues
>         fonts              - Different fonts
>         foomatic           - Foomatic DB, DB engine, filters
>         illumos           - Components, specific to OI/illumos
>         inputmethod           - Input Method -related things
>         libusb           - libusb
>         meta-packages      - Meta packages, which doesn't deliver 
> actual files
>         openoffice           - OpenOffice and OpenOffice dmake
>         openssl            - Different OpenSSL versions
>         osol               - packages, which we republish from 
> opensolaris.org repository with some changes
>         perl               - Different Perl versions
>         perl_modules       - Perl Modules
>         python             - Python and Python libraries
>         ruby               - Ruby and Ruby libraries
>         samba              - Different samba versions
>         scientific         - Scientific components
>             scientific/python  - Scientific python modules
>         sqlite             - Sqlite and tcl sqlite library
>         tcl                - tcl, tk and tcl libraries
>         x11                - x11 components
>         xscreensaver       - xscreensaver and rss-glx
>
> And about 700 uncategorized components.
>
> This is an awful mess!!!!
>
> I'd like to move to something more similar to pkgsrc or ports structure.
>
> Ports categories:
> accessibility
> arabic
> archivers
> astro
> audio
> benchmarks
> biology
> cad
> chinese
> comms
> converters
> databases
> deskutils
> devel
> dns
> editors
> emulators
> finance
> french
> ftp
> games
> german
> graphics
> hebrew
> hungarian
> irc
> japanese
> java
> korean
> lang
> mail
> math
> misc
> multimedia
> net
> net-im
> net-mgmt
> net-p2p
> news
> packages
> palm
> polish
> ports-mgmt
> portuguese
> print
> russian
> science
> security
> shells
> sysutils
> textproc
> ukrainian
> vietnamese
> www
> x11
> x11-clocks
> x11-drivers
> x11-fm
> x11-fonts
> x11-servers
> x11-themes
> x11-toolkits
> x11-wm
>
>
> Pkg-src categories:
> archivers
> audio
> benchmarks
> biology
> bootstrap
> cad
> chat
> comms
> converters
> cross
> databases
> devel
> editors
> emulators
> filesystems
> finance
> fonts
> games
> geography
> graphics
> ham
> inputmethod
> lang
> mail
> math
> mbone
> meta-pkgs
> misc
> multimedia
> net
> news
> packages
> parallel
> pkglocate
> pkgtools
> print
> regress
> security
> shells
> sysutils
> textproc
> time
> wm
> www
> x11
>
> The issue is that moving component from top level components directory 
> to subdirectory will trigger build in Jenkins, which requires some 
> (and sometimes considerable) time, can require fixing some components, 
> and so is better to be avoided as one-time task.
>
> I suggest:
> 1) agree on several (~20 ) categories (something like in pkg-src);
> 2) move individual components to corresponding categories as they are 
> touched;
> 3) avoid creating new top-level components;
> 4) allow creating sub-categories.
>
> As for top-level categories, I'd like to see something like
>
> archivers
> closed      # closed source components
> databases
> devel      # development tools and libraries
> desktop-environments # gnome, enlightenment\
> deskutils
> encumbered
> fonts
> games
> graphics
> lang       # languages and language modules
> inputmethod
> meta-packages
> multimedia
> openindiana # illumos and OI-specific software
> scientific
> shells
> sysutils
> textproc
> www
> x11
>
>
> What do you think?
>
>
>
>
Good idea,
As I am not familiar with pkg-src I would look at FreeBSD's ports.
What is the difference between lang and devel? For me the distinction
is sometimes arbitrary.

Regards
Andreas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/oi-dev/attachments/20160218/fba1c206/attachment-0005.html>


More information about the oi-dev mailing list