discuss: Developing documented Linux stacks


Previous by date: 12 Mar 2012 08:55:07 +0000 Re: Developing documented Linux stacks, Alexey Eromenko
Next by date: 12 Mar 2012 08:55:07 +0000 Migrating TLDP from CVS to Git., W. Trevor King
Previous in thread: 12 Mar 2012 08:55:07 +0000 Re: Developing documented Linux stacks, Alexey Eromenko
Next in thread:

Subject: Re: Developing documented Linux stacks
From: Roger ####@####.####
Date: 12 Mar 2012 08:55:07 +0000
Message-Id: <20120312085454.GB2753@localhost2.local>

> On Mon, Mar 12, 2012 at 01:27:34AM +0200, Alexey Eromenko wrote:
>> Did I get this right, or did I fail miserably?
>You fail miserably. Stack is a set of related dependencies.
>
>See my diagrams.

These are diagrams of package dependencies for a specific function a user is 
trying to configure their GNU/Linux system for.  The diagrams further detail 
where the each package dependency will lie within the execution (memory) stack.

ie.

Click & Play KDE/iCKy Interface
Xine/FFMpeg user frontends
Also/OSS userspace libs/utilities
Alsa/OSS drivers
Linux Kernel 

I was correct.  I started second guessing when I took a second closer look just 
now thinking they were only package dependencies.  But the diagrams do detail 
the stack.

(The stack grows from the bottom up.)

-- 
Roger
http://rogerx.freeshell.org/

Previous by date: 12 Mar 2012 08:55:07 +0000 Re: Developing documented Linux stacks, Alexey Eromenko
Next by date: 12 Mar 2012 08:55:07 +0000 Migrating TLDP from CVS to Git., W. Trevor King
Previous in thread: 12 Mar 2012 08:55:07 +0000 Re: Developing documented Linux stacks, Alexey Eromenko
Next in thread:


  ©The Linux Documentation Project, 2014. Listserver maintained by dr Serge Victor on ibiblio.org servers. See current spam statz.