[puppy-devel] Re: Why base SelfHostingPuppy M5 on anything other than M4?
- From: Fran Boon <flavour@xxxxxxxxxxxxx>
- To: puppy-devel@xxxxxxxxxxxxx
- Date: Fri, 10 Feb 2006 12:36:38 +0000
Jonathan Marsden wrote:
Fran has edited the page at http://puppylinux.org/wikka/SelfHostingPuppy
to suggest that M5, the initial graphical Puppy variant that is built
entirely from source as a result of the SelfHostingPuppy project, be
based on EmtpyCrust.
I don't understand how it can be, since EmptyCrust is not built from
source, which is the primary goal of SelfHostingPuppy.
We can perhaps take ideas on what we can safely omit by looking at the
EmtpyCrust package list, but "based on" suggests a more direct link. How
can that work, and yet still ensure the whole of the result is built
from source under Puppy itself? What would the project gain by
switching from M4 "Puppy Commander" to Empty Crust as a base for M5?
I'm confused by this new suggestion... please help me to understand it.
Exactly what you logically thought I could mean:
"take ideas on what we can safely omit by looking at the EmptyCrust
package list"
You wanted a working subset which omitted the heavier apps...EmptyCrust
is just that.
Of course the exact mix could be slightly different, but why re-invent
the wheel :)
I certainly have a different mix in my variant, but then I also add some
big stuff, so mine wouldn't be a suitable template...
F
PS All your posts hit my spam filter :/
8.0 RAZOR2_CHECK Listed in Razor2 (http://razor.sf.net/)
- References:
- [puppy-devel] Why base SelfHostingPuppy M5 on anything other than M4?
- From: Jonathan Marsden
Other related posts:
- » [puppy-devel] Why base SelfHostingPuppy M5 on anything other than M4?
- » [puppy-devel] Re: Why base SelfHostingPuppy M5 on anything other than M4?
Fran has edited the page at http://puppylinux.org/wikka/SelfHostingPuppy to suggest that M5, the initial graphical Puppy variant that is built entirely from source as a result of the SelfHostingPuppy project, be based on EmtpyCrust. I don't understand how it can be, since EmptyCrust is not built from source, which is the primary goal of SelfHostingPuppy. We can perhaps take ideas on what we can safely omit by looking at the EmtpyCrust package list, but "based on" suggests a more direct link. How can that work, and yet still ensure the whole of the result is built from source under Puppy itself? What would the project gain by switching from M4 "Puppy Commander" to Empty Crust as a base for M5? I'm confused by this new suggestion... please help me to understand it.
- [puppy-devel] Why base SelfHostingPuppy M5 on anything other than M4?
- From: Jonathan Marsden