<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Am 18.02.16 um 10:30 schrieb Alexander
Pyhalov:<br>
</div>
<blockquote cite="mid:56C58F4E.2070105@rsu.ru" type="cite">Hi.
<br>
<br>
Today I wanted to add myspell dictionaries to oi-userland.
<br>
As OI dictionaries are based on dictionaries from OpenOffice.org,
disappeared long ago, I wanted to base them on Debian dictionaries
<br>
(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.
<br>
<br>
Let's look, currently we have the following "categories" - i.e.
directories under components, containing another components:
<br>
<br>
apache2-modules - Apache 2.2 and 2.4 modules
<br>
aspell - Aspell and its dictionaries
<br>
autoconf - Different autoconf versions
<br>
automake - Different automake versions
<br>
common-lisp - common lisp libraries
<br>
docbook - docbook stylesheets/dtds
<br>
e - Enlightenment
<br>
encumbered - components which shouldn't appear
in main repository due to patent issues
<br>
fonts - Different fonts
<br>
foomatic - Foomatic DB, DB engine, filters
<br>
illumos - Components, specific to OI/illumos
<br>
inputmethod - Input Method -related things
<br>
libusb - libusb
<br>
meta-packages - Meta packages, which doesn't deliver
actual files
<br>
openoffice - OpenOffice and OpenOffice dmake
<br>
openssl - Different OpenSSL versions
<br>
osol - packages, which we republish from
opensolaris.org repository with some changes
<br>
perl - Different Perl versions
<br>
perl_modules - Perl Modules
<br>
python - Python and Python libraries
<br>
ruby - Ruby and Ruby libraries
<br>
samba - Different samba versions
<br>
scientific - Scientific components
<br>
scientific/python - Scientific python modules
<br>
sqlite - Sqlite and tcl sqlite library
<br>
tcl - tcl, tk and tcl libraries
<br>
x11 - x11 components
<br>
xscreensaver - xscreensaver and rss-glx
<br>
<br>
And about 700 uncategorized components.
<br>
<br>
This is an awful mess!!!!
<br>
<br>
I'd like to move to something more similar to pkgsrc or ports
structure.
<br>
<br>
Ports categories:
<br>
accessibility
<br>
arabic
<br>
archivers
<br>
astro
<br>
audio
<br>
benchmarks
<br>
biology
<br>
cad
<br>
chinese
<br>
comms
<br>
converters
<br>
databases
<br>
deskutils
<br>
devel
<br>
dns
<br>
editors
<br>
emulators
<br>
finance
<br>
french
<br>
ftp
<br>
games
<br>
german
<br>
graphics
<br>
hebrew
<br>
hungarian
<br>
irc
<br>
japanese
<br>
java
<br>
korean
<br>
lang
<br>
mail
<br>
math
<br>
misc
<br>
multimedia
<br>
net
<br>
net-im
<br>
net-mgmt
<br>
net-p2p
<br>
news
<br>
packages
<br>
palm
<br>
polish
<br>
ports-mgmt
<br>
portuguese
<br>
print
<br>
russian
<br>
science
<br>
security
<br>
shells
<br>
sysutils
<br>
textproc
<br>
ukrainian
<br>
vietnamese
<br>
www
<br>
x11
<br>
x11-clocks
<br>
x11-drivers
<br>
x11-fm
<br>
x11-fonts
<br>
x11-servers
<br>
x11-themes
<br>
x11-toolkits
<br>
x11-wm
<br>
<br>
<br>
Pkg-src categories:
<br>
archivers
<br>
audio
<br>
benchmarks
<br>
biology
<br>
bootstrap
<br>
cad
<br>
chat
<br>
comms
<br>
converters
<br>
cross
<br>
databases
<br>
devel
<br>
editors
<br>
emulators
<br>
filesystems
<br>
finance
<br>
fonts
<br>
games
<br>
geography
<br>
graphics
<br>
ham
<br>
inputmethod
<br>
lang
<br>
mail
<br>
math
<br>
mbone
<br>
meta-pkgs
<br>
misc
<br>
multimedia
<br>
net
<br>
news
<br>
packages
<br>
parallel
<br>
pkglocate
<br>
pkgtools
<br>
print
<br>
regress
<br>
security
<br>
shells
<br>
sysutils
<br>
textproc
<br>
time
<br>
wm
<br>
www
<br>
x11
<br>
<br>
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.
<br>
<br>
I suggest:
<br>
1) agree on several (~20 ) categories (something like in pkg-src);
<br>
2) move individual components to corresponding categories as they
are touched;
<br>
3) avoid creating new top-level components;
<br>
4) allow creating sub-categories.
<br>
<br>
As for top-level categories, I'd like to see something like
<br>
<br>
archivers
<br>
closed # closed source components
<br>
databases
<br>
devel # development tools and libraries
<br>
desktop-environments # gnome, enlightenment\
<br>
deskutils
<br>
encumbered
<br>
fonts
<br>
games
<br>
graphics
<br>
lang # languages and language modules
<br>
inputmethod
<br>
meta-packages
<br>
multimedia
<br>
openindiana # illumos and OI-specific software
<br>
scientific
<br>
shells
<br>
sysutils
<br>
textproc
<br>
www
<br>
x11
<br>
<br>
<br>
What do you think?
<br>
<br>
<br>
<br>
<br>
</blockquote>
<font size="+1">Good idea,<br>
As I am not familiar with pkg-src I would look at FreeBSD's ports.<br>
What is the difference between lang and devel? For me the
distinction<br>
is sometimes arbitrary.<br>
<br>
Regards<br>
Andreas<br>
<br>
</font>
</body>
</html>