Branden Robinson wrote:
> On Mon, May 14, 2001 at 10:05:22PM -0400, Joey Hess wrote:
> > - With package sets, it is delivered ... ?
>
> In a package called package-sets-progeny, and manipulated via binaries in
> the packages pkgset-tools and pkgset-tools-gnome.
Ok, then this has basically the sam
On Mon, May 14, 2001 at 10:05:22PM -0400, Joey Hess wrote:
> - With package sets, it is delivered ... ?
In a package called package-sets-progeny, and manipulated via binaries in
the packages pkgset-tools and pkgset-tools-gnome.
--
G. Branden Robinson | What influenced me to ath
On Mon, May 14, 2001 at 10:02:53PM -0400, Joey Hess wrote:
> Anthony Towns wrote:
> > For comparison, using task- packages, if I remove the core packages from
> > a task from woody, I can just also remove the task- from woody.
> In a sense, doing it programmatically is cleaner and less work in the
Branden Robinson wrote:
> We have "package sets".
>
> Here's an example:
>
> /usr/share/package-sets/progeny/xemacs.contents
> /usr/share/package-sets/progeny/xemacs.description
>
> $ cat /usr/share/package-sets/progeny/xemacs.contents
> xemacs21
> xemacs21-bin
> xemacs21-mule
> xemacs21-support
Anthony Towns wrote:
> > enhancements to deal with cases where all the packages in a task, or at
> > least some of the important ones, are missing. Noticing all are missing
> > and not displaying the task in the list is easy enough. Noticing that
> > the core packages of a task (postgresl, apache)
On Sat, May 12, 2001 at 01:39:43PM -0400, Joey Hess wrote:
> Anthony Towns wrote:
> Also, this is one of the reasons I think we should give people the
> opportunity to drop into dselect/something better after broadly
> outlining their tasks to they can tweak the result if necessary.
> I think we sh
On Sat, May 12, 2001 at 01:39:43PM -0400, Joey Hess wrote:
> (BTW, could someone from Progeny PLEASE speak up and give us a summary
> of how your task analog works?)
I'd tell you in IRC, but whoops, for no apparent reason I've been banned
from the channel. Probably by someone who has said in the
Anthony Towns wrote:
> you can't see the packages that comprise a task or their descriptions, nor
> can you include a long description. ie, the whole "Task Info" thing's
> missing.
I don't think that's very important. A task is supposed to satisfy a
simple, well-defined need. If you want a web ser
On Wed, May 09, 2001 at 04:57:13PM -0400, Joey Hess wrote:
> Attached to this message is a tarball which contains a rather simple
> program that uses debconf to present the user with a list of tasks
> (sorted into groups).
Are you serious?
No, really, are you?
I can't see any hint that you're no
Hi
Using debconf for tasks would also make all the current and
future interfaces available for task selection.
Joey Hess schrieb:
> [EMAIL PROTECTED]:~/tmp/newtasksel>./tasksel -t tasklist
> Selecting software to install
> -
>
> A Debian system can be used for many ta
Attached to this message is a tarball which contains a rather simple
program that uses debconf to present the user with a list of tasks
(sorted into groups). To try it, upgrade to debconf 0.9.53 (Incoming) [1],
unpack, and run "newtasksel/tasksel -t newtasksel/tasklist"
(or see [2] at the very end
11 matches
Mail list logo
