[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Those task packages



On Sun, 17 Mar 2002, Joey Hess wrote:

> > Now the good news.  
> > desktop
> > laptop
> > dialup
> > print-server
> > unix-server	make up a 542765K first CD.
> 
> That looks good. If you need to gain space I'd suggest demoting
> unix-server to a later cd.
> 
> Have you checked for any other partial overlaps with other tasks that
> are not in the above list?

c-dev
chinese-s
chinese-t
file-server
games
german
japanese
korean
laptop
mail-server
polish
python-dev
russian
spanish
tex

 
> > We have a real problem now there two are important CDs
> 
> What't the other one, language stuff?

junior
games
science
file-server
c-dev
dns-server
mail-server
news-server
tex
python-dev
tcltk-dev
polish
russian
spanish
fortran-dev
german
japanese
korean
chinese-s
cyrillic
french
chinese-t
database-server

I think that there is one or two missing from the list.  The is room for
some more on the first CD.
 
> > and there is no way
> > we can work round this issue, and it will be worse in twelve months. The
> > simple solution is to go the Red Hat way and say "use the two CDs or
> > else". 
> 
> "or else network", which everyone will really be doing anyway, right?
> 
> I figure the only people who will have only one CD and no network are
> probably a rasonably close match with people who just want a desktop.

Agreed. And I would add those who only want an initial installation and
use a network for everything else.  I have not checked to see what apps
are included in desktop, but we could use the extra space for some nice
stuff.  Provided that we have made provision for every kind of network
installation on the first CD.

> > Another suggestion, use dummy packages, these would not be the same as the
> > potato task-* packages.  tasksel would look for these new task-* packages
> > and if it found task-foo it would only then offer foo in its menu.  There
> > would still be a Task: field so these dummy packages would be included in
> > tasks/task-woody.  These would not have to be maintained as they would be
> > fully functional as long as the particular task remained in existence
> > regardless of changes within that task. If people really wanted to be
> > sophisticated then they could be designed not to be installed. 
> 
> It's the same effect as marking packages in tasks as essential to that
> task, and omitting to show the task unless they are available. If
> necessary we can surely come up with something post-woody.

IMHO we need to come up with something for woody.

Only one representative package needs to be marked, provided that foo is
the only task in the Task: field.  eg asiya24-vfont for japanese,
doc-linux-pl for polish, inn2 for news-server etc.  These will not be
found on the first CD unless the task has be specifically nominated. 
Something like "Task: foo master" for these packages?  AFAIK, the Task:
field only occurs in the Packages file and not the package's control, so
it should not be difficult to implement, mind you I have not really
investigated this.  Some hacking of tasksel and a modification to how the
Packages files are built would be needed. 

> 
> We need DVD's.

In time, the last time I investigated these the cost per GB was about x3
the cost of CD-Rs.

Phil.

--
  Philip Charles; 39a Paterson Street, Abbotsford, Dunedin, New Zealand
   +64 3 488 2818        Fax +64 3 488 2875        Mobile 025 267 9420
     philipc@copyleft.co.nz - preferred.          philipc@debian.org
     I sell GNU/Linux & GNU/Hurd CDs.   See http://www.copyleft.co.nz



Reply to: