I dunno, it seems there is a pretty consistent naming convention for packages that contain ubuntu specifics: 'aptitude search ubuntu' gives: ... edubuntu-addon-kde edubuntu-addon-legacy edubuntu-addon-light edubuntu-addon-science ... kubuntu-artwork-kbfx kubuntu-artwork-usplash kubuntu-default-settings kubuntu-desktop kubuntu-docs kubuntu-grub-splashimages kubuntu-konqueror-shortcuts kubuntu-restricted-extras linux-ubuntu-modules-2.6.22-7-... ... ubuntu-artwork ubuntu-calendar ubuntu-calendar-december ubuntu-calendar-february ubuntu-calendar-january ubuntu-calendar-march ubuntu-calendar-november ubuntu-calendar-october ubuntu-desktop ubuntu-docs ubuntu-keyring ubuntu-laptop-mode ubuntu-minimal ubuntu-mobile ...
You get the picture. What's to gain by breaking this pattern?
I dunno, it seems there is a pretty consistent naming convention for packages that contain ubuntu specifics: addon-legacy addon-light addon-science artwork- kbfx artwork- usplash default- settings grub-splashimag es konqueror- shortcuts restricted- extras modules- 2.6.22- 7-... calendar- december calendar- february calendar- january calendar- march calendar- november calendar- october
'aptitude search ubuntu' gives:
...
edubuntu-addon-kde
edubuntu-
edubuntu-
edubuntu-
...
kubuntu-
kubuntu-
kubuntu-
kubuntu-desktop
kubuntu-docs
kubuntu-
kubuntu-
kubuntu-
linux-ubuntu-
...
ubuntu-artwork
ubuntu-calendar
ubuntu-
ubuntu-
ubuntu-
ubuntu-
ubuntu-
ubuntu-
ubuntu-desktop
ubuntu-docs
ubuntu-keyring
ubuntu-laptop-mode
ubuntu-minimal
ubuntu-mobile
...
You get the picture. What's to gain by breaking this pattern?