[gentoo-dev] A new category scheme idea

* [gentoo-dev] A new category scheme idea
@ 2002-02-04  7:19 Einar Karttunen
  2002-02-04 11:25 ` gentoo-user
  0 siblings, 1 reply; 7+ messages in thread
From: Einar Karttunen @ 2002-02-04  7:19 UTC (permalink / raw
  To: gentoo-dev

Hello

I have thought about a new way of categorise ebuilds in gentoo. The
new scheme would be based on category files which would be just a
list of dependencys as portage understands them. Each package could
be in many categories and categories may include categories (but there
may be no circular references). 

So the category files would be essentially just the contents of the directories
initially, but they are easily extensible. For example the dev-lisp category 
could be represented by the following file:
ecls
gcl
sbcl

Of course in additional to these categories we may create additional categories
for example we could create a web-server-apps category which would include
all apps needed for a typical web-server. Also we could have a suggested
base system category which would include all apps which are essential
in creating a functional system...

This scheme grows even more attractive if there is a gui-installer, because
it has just to understand categories. This would also solve all gnome/kde-apps
vs. other categories problems, as the applications could be included
in both categories.

But how much worl would this be? I am not entirely familiar with the portage
source code, but it seems quite modular, so there should be no large problems.
Things that would have to be done:
* switch /var/db/pkg not to use categories, but just package names. This
  should be simple to implement.
* flatten /usr/portage all apps would be moved from their category directories
  to a common directory
* remove category directories from portage, should be quite simple
* add support for category files to emerge. The algorithm could
  be if the target is an application/ebuild proceed as before
  if it is a category merge all files in that category (this could
  be handled using the existing dependency code). Support also syntax
  like emerge category/abc which should also be quite easy to implement
  (open category file and fed the line matching abc to the dependency
  handling mechanism).
* replace DEPEND="a/b c/d" in all ebuilds by DEPEND="b d". 
* make changes in gentolkit
* make something for new users with menus

This sould also make portage faster than now when emerging a build
without a category name, because all applications are in the same
directory. Of course we sould move /usr/portage to /var/portage,
because /usr should contain only read-only data :-)
It may seem that directories are more clear for manual operations
but they would have their own operations like:
ls /usr/portage/app-admin => cat /vat/portage/app-admin.cat

- Einar Karttunen

^ permalink raw reply	[flat|nested] 7+ messages in thread