alternative puppy build system
-
- Posts: 721
- Joined: Sat 31 Mar 2018, 08:01
- Location: Rakaia
- Contact:
-
- Posts: 721
- Joined: Sat 31 Mar 2018, 08:01
- Location: Rakaia
- Contact:
-
- Posts: 721
- Joined: Sat 31 Mar 2018, 08:01
- Location: Rakaia
- Contact:
hi all
unfortunately after analyzing jamesbonds woof-ce
i have come to the conclusion that that kind of a system
cannot produce the kind of distro i envision
it is a neat system
and very fast and easy to use
but like all woof-ce clones it weaves all the pieces together
this is incompatible with a modular system
so i will go back to the system that i devised
which is a modular approach
that means that upupbb32 will once again be the base of this project
and a1.iso and a2.iso will be what we are working on
i do however want to thank jamesbond for making his woof-ce available
and for inspiring this project
and for all his help and support
i will correct the first post to reflect this
wanderer
unfortunately after analyzing jamesbonds woof-ce
i have come to the conclusion that that kind of a system
cannot produce the kind of distro i envision
it is a neat system
and very fast and easy to use
but like all woof-ce clones it weaves all the pieces together
this is incompatible with a modular system
so i will go back to the system that i devised
which is a modular approach
that means that upupbb32 will once again be the base of this project
and a1.iso and a2.iso will be what we are working on
i do however want to thank jamesbond for making his woof-ce available
and for inspiring this project
and for all his help and support
i will correct the first post to reflect this
wanderer
hi all
this is an announcement that this project
will support 2 alternative build systems for puppy
1. my modular build system
which builds a modular puppy
2. and jamesbonds woof-ce next
which builds a standard puppy
i will need help to develop both
so if you are interested
please post on this thread
have a nice day
wanderer
this is an announcement that this project
will support 2 alternative build systems for puppy
1. my modular build system
which builds a modular puppy
2. and jamesbonds woof-ce next
which builds a standard puppy
i will need help to develop both
so if you are interested
please post on this thread
have a nice day
wanderer
hi all
i my opinion the key to making jamesbonds woof-ce next
more manageable
is to make is search for a smaller repository of components
just the puppy woof-ce repository
then we wouldnt have to be concerned
with the constantly changing big distros
we could then over time build a small repository
just for jamesbonds woof-ce next
with just the stuff we wanted
we could access components from other distros
and make them into woof-ce next components
and put them in the woof-ce next repository for our use later
this is what i am trying to do now
any help would be appreciated
wanderer
i my opinion the key to making jamesbonds woof-ce next
more manageable
is to make is search for a smaller repository of components
just the puppy woof-ce repository
then we wouldnt have to be concerned
with the constantly changing big distros
we could then over time build a small repository
just for jamesbonds woof-ce next
with just the stuff we wanted
we could access components from other distros
and make them into woof-ce next components
and put them in the woof-ce next repository for our use later
this is what i am trying to do now
any help would be appreciated
wanderer
You mean just convert the core of what we need from another distro into a pet and put it into a new repository?wanderer wrote:hi all
i my opinion the key to making jamesbonds woof-ce next
more manageable
is to make is search for a smaller repository of components
just the puppy woof-ce repository
then we wouldnt have to be concerned
with the constantly changing big distros
we could then over time build a small repository
just for jamesbonds woof-ce next
with just the stuff we wanted
we could access components from other distros
and make them into woof-ce next components
and put them in the woof-ce next repository for our use later
this is what i am trying to do now
any help would be appreciated
wanderer
hi a243a
yes just take any component of any system
convert it into a pet and put it in
the jamesbond woof-ce next repository
then have his system load it into a puppy
that way you can make the puppy a combination of all systems
and you wouldnt have to worry about
keeping up with the changes of the big distros
that is what i am trying to figure out how to do now
wanderer
yes just take any component of any system
convert it into a pet and put it in
the jamesbond woof-ce next repository
then have his system load it into a puppy
that way you can make the puppy a combination of all systems
and you wouldnt have to worry about
keeping up with the changes of the big distros
that is what i am trying to figure out how to do now
wanderer
pkg or puppy build
We can already install .deb .txz .rpm ... to Puppy. Or is this not what you mean with 'components of any system'?wanderer wrote:hi a243a
yes just take any component of any system
convert it into a pet and put it in
the jamesbond woof-ce next repository
then have his system load it into a puppy
that way you can make the puppy a combination of all systems
and you wouldnt have to worry about
keeping up with the changes of the big distros
that is what i am trying to figure out how to do now
wanderer
Should we not consider to compile in the base Puppy, instead of having a repository?
In that case petbuilds in woof CE could be interesting.
But even more so Pkg from sc0ttman, one of the best things created in Puppyland on the last years:
Pkg - CLI package manager
Just my idea.