Modules -> Devel or Lib should be read as Modules -> Lib

I understand why nforce and nvidia were not put into Modules: because they didn't contain kernel modules - only source and installer.
But now (I mean new packages in [testing]) they are packaged the same way as ati-fglrx, so they should be in Modules section.

the perl things are also modules of perl. this was the first idea for the modules section. i might be needed to change it, i will assign it to apeiro and see what he thinks..

Maybe then this category should be split to Kernel-Modules and Perl-Modules? Or all kernel modules and kernels should be in one Kernel category, leaving Modules for Perl/Python/etc modules?
Anyway, I like how this is done in Frugalware: they have fwcpan for installing Perl modules from CPAN. For management and dependency tracking fwcpan works with fwpacman which has support for this functionality.

The situation with Modules section in AUR is even worse. There are even packages that are not kerlel nor Perl or Python modules. I think that changes in Arch repository (if they will be made) should be followed by the same changes in AUR, so I don't feel that filing another bug report for AUR is necessary.

IMHO these packages should be in Modules too:
lirc
lirc-beyond
lirc-utils

Updated list:

OK:
ati-fglrx
ati-fglrx-beyond
ati-fglrx-utils
kernel26-km
squashfs
squashfs-beyond
unionfs
unionfs-beyond
unionfs-utils
madwifi-ng
madwifi-ng-beyond
madwifi-ng-utils
rt2500
rt2500-beyond
rt2x00
rt2x00-beyond
tiacx
tiacx-beyond
tiacx-firmware

System -> Modules:
nforce
nforce-beyond
nforce-utils
lirc
lirc-beyond
lirc-utils
squashfs-tools -> squashfs-utils

X11 -> Modules:
nvidia
nvidia-beyond
nvidia-legacy
nvidia-legacy-beyond
nvidia-legacy-utils
nvidia-utils

Network -> Modules:
fcpci
fcpci-beyond
fcpcmcia
fcpcmcia-beyond
intel-536ep
intel-536ep-beyond
intel-536ep-utils
intel-537
intel-537-beyond
intel-537-utils
ipw3945
ipw3945-beyond
ipw3945-ucode
ipw3945d -> ipw3945-utils
ltmodem
ltmodem-beyond
ltmodem-utils
madwifi
madwifi-beyond
madwifi-utils
ndiswrapper
ndiswrapper-beyond
ndiswrapper-utils
slmodem
slmodem-beyond
slmodem-utils
wlan-ng26
wlan-ng26-beyond
wlan-ng26-utils

Modules -> Lib:
perl-extutils-depends
perl-extutils-pkgconfig
perl-module-build
perl-string-shellquote
python-numeric

As for Perl modules in Modules: IMHO they should be handled by some utility like perl-cpanplus-pacman (http://bbs.archlinux.org/viewtopic.php?t=21048) which can be integrated with Pacman (like fwcpan in Frugalware).

Multimedia -> Xorg11-drivers:
openchrome

Roman I don't believe nvidia-utils should belong to modules, that's user space stuff hence it should be stored in the x11-drivers section, shouldn't it?

forgive my ignorance on the matter, but what exactly is the purpose of grouping packages into "sections"?

Easier to find via web interface and CVS.

Yeah, this is a good idea - we need some cleanup. Anyone want to volunteer to clean up CVS?

Since we're going to change our SCM structure and it won't have categories directories - this report is partly obsoleted now.
IMO we need to develop a better category tree and a way to bind package to category (probably even to multiple categories, or use tag-based categorization).

I like the idea of tag-based categories.

Categories no longer exist in the svn repos... is this closable? I think it may be.

See also: FS#7132