[Peeweelinux-devel] Re: DOC Docs

[Adi Linden]

Hi Mark,

I am documenting all the steps I take to create the development 
environment. This means it will be possible to actually PeeWeeLinux from 
scratch using a bunch of scripts. This would include downloading the 
sources from the original sites (I.e. gcc from gnu.org).

I am thinking about a directory structure similar to what's below. This 
might seem awkward at first, but it will allow for chroot to /peeweelinux 
and building of packages within the chrooted environment. Now it won't 
mater any longer what underling Linux distribution is used for 
PeeWeeLinux.

When RPMS are build, a <packagename>-devel rpm would be build for the sole 
purpose of installing in the chrooted environment. This will make it easy 
to link against just the libs that are part of PeeWeeLinux.

Any thoughts on this? 

/peeweelinux
  |
  +---- /tools
  |       |
  |       +---- /pwlconfig -  directory containing the pwlconfig scripts
  |       |
  |       +---- /backups   -  directory to store project backups
  |       | 
  |       +---- /examples  -  directory to store provided example projects
  |       |
  |       +---- /docs      -  directory for PeeWeeLinux documentation
  |       |
  |       +---- /specs     -  spec files for PeeWeeLinux RPMS
  |       |
  |       +---- /scratch   -  directory containing scripts
  |       |                   to build environment from scratch and
  |       |                   patches necessary for static build tools
  |       |
  |       +---- /lxdialog  -  the lxdialog sources
  |
  +---- /bin
  |
  +---- /dev
  |
  +---- /home
  |
  +---- /lib
  |
  +---- /usr
  |       |
  |       +---- /src
  |       |       |
  |       |       +---- /peeweelinux
  |       |       |       |
  |       |       |       +---- SPECS (symlink to ../../../../tools/specs)
  |       |       |       |
  |       |       |       +----> BUILD, SOURCES, RPMS, SRPMS ...
  |       |       |
  |       |       +---- /scratch  - directory for non-rpm sources for
  |       |                         building static tools
  |       |
  |       +----> /bin, /sbin, /share, etc ...
  |
  +---- /etc, /mnt, /sbin, /tmp, etc ...

Regards,
Adi


> I kind of like the way the Linux Router Project guys do things like this.  They have
> something called a "LRP" package, and it's fairly easy for a novice user to grab
> additional LRP packages, and integrate them into their project.  For the power users,
> there's good documentation on how to build LRP packages from scratch, and contribute them.
>
> It seems like they have "core" distributions, containing the basic required packages, and
> then the user can expand on the basic system by using as many LRP packages as space
> permits.  Each of these additional LRP packages aren't necessarily part of the core
> distribution; users simply download individual packages as needed.  I don't know if these
> LRP concepts are relevant to Peewee, but I thought I'd pass it along.
> 
> Regardless of the implementation, coming up with an easy way for people to contribute
> additional packages is a great idea!  You've really got a great thing going here, and I'm
> among the many people who want to help make it better.  Whatever you come up with, I'd be
> glad to help develop, test, and document it.
> 
> We probably should take this discussion to the list.  I've already seen a number of really
> good suggestions and ideas out there.
> 
> Regards,
> 
> Mark
> 
> P.S.  I've (temporarily) posted my DiskOnChip/Peewee instructions to my website.  I've
> been corresponding with a board vendor (http://www.c2central.com/page514613.htm) that is
> interesting in using Peewee.
> 
> I used their UIB product for one of my clients, and I have another project where I might
> end up using it again.  Their 8MB DoC comes with preinstalled Redhat 6.2, but was more
> aimed at a specific application, rather than a "generic" Linux distribution.  I used
> Peewee to start over from scratch -- worked great!
>