woof-CE needs you
@musher0
Devuan, Debian, Ubuntu, Trisquel (from Iguleder's fork) and to a degree Slackware should all build fine.
We should probably put in a mechanism that detects if config files for a certain distro haven't been touched for an arbitrary amount of time (say 100 days?) and pop a warning that there may be certain failures.
Mageia, Arch and T2 haven't been touched for quite a while.
Devuan, Debian, Ubuntu, Trisquel (from Iguleder's fork) and to a degree Slackware should all build fine.
We should probably put in a mechanism that detects if config files for a certain distro haven't been touched for an arbitrary amount of time (say 100 days?) and pop a warning that there may be certain failures.
Mageia, Arch and T2 haven't been touched for quite a while.
Puppy Linux Blog - contact me for access
- Iguleder
- Posts: 2026
- Joined: Tue 11 Aug 2009, 09:36
- Location: Israel, somewhere in the beautiful desert
- Contact:
You should have read the first post carefully. I don't like this hostile attitude.musher0 wrote:Now he tells us...
All Trisquel support is in woof-CE. My fork has only the files under woof-distro (the package list, etc').01micko wrote:Devuan, Debian, Ubuntu, Trisquel (from Iguleder's fork) and to a degree Slackware should all build fine.
I want this solution to be git rm. Configuration files for unsupported or old distros should be deleted. And yes, if we don't actively support Magiea, T2 and other distros that code should be removed. Less code - less bugs.01micko wrote:We should probably put in a mechanism that detects if config files for a certain distro haven't been touched for an arbitrary amount of time (say 100 days?) and pop a warning that there may be certain failures.
[url=http://dimakrasner.com/]My homepage[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
[url=https://github.com/dimkr]My GitHub profile[/url]
Hello again.
At the build iso question, I answered "(space)ENTER", but it still went
ahead with burning. Although the script said: "type any character then
Enter if you don't want to burn."
I thought (space) was a valid ASCII character!
Luckily I'm a character too, and my dvd was unusable.
(Don't look for any relevance, there isn't any!)
The script also warned me that Bacon dev was not in the devx, with some
instructions how to include it. A bit late now, I'd say! while it's
squishing the devx.
This is lots of fun!
musher0
At the build iso question, I answered "(space)ENTER", but it still went
ahead with burning. Although the script said: "type any character then
Enter if you don't want to burn."
I thought (space) was a valid ASCII character!
Luckily I'm a character too, and my dvd was unusable.
(Don't look for any relevance, there isn't any!)
The script also warned me that Bacon dev was not in the devx, with some
instructions how to include it. A bit late now, I'd say! while it's
squishing the devx.
This is lots of fun!
musher0
Last edited by musher0 on Sat 03 Oct 2015, 23:45, edited 1 time in total.
That was Barry's. If you wanted to leverage Barry's latest T2 packages you could point the repos to Barry's quirky repo (x86 or x86_64) but there would need to be changes in all the setup scripts to accommodate T2_64.Ted Dog wrote:Ok has T2 ever been built? that is where I was heading in my learning trip with WolfCE. could be my SECOND try after a Slacko64 try.
So, learn woof-ce, build a slacko64, then keep your fork updated, make changes for T2, build it, break it, rebuild it, repeat and then push (issue pull request) the result.
Puppy Linux Blog - contact me for access
Yikes and yikes!
I'm going for a Trusty so it shouldn't be a problem but Musher0 does have a point. The process is pretty long, so we should probably have a list of what not to make. I mean, imagine going through this long download process and get something that doesn't work. Now that's a pretty mean joke, though unintentional, I'm sure.
If I may, I'd like to take the time to thank the programmers for all their efforts. You're all pretty fantastic, so take a bow....
Best,
Slavvo67
I'm going for a Trusty so it shouldn't be a problem but Musher0 does have a point. The process is pretty long, so we should probably have a list of what not to make. I mean, imagine going through this long download process and get something that doesn't work. Now that's a pretty mean joke, though unintentional, I'm sure.
If I may, I'd like to take the time to thank the programmers for all their efforts. You're all pretty fantastic, so take a bow....
Best,
Slavvo67
My God! Such compunction. Cops react like that when someone has aIguleder wrote:You should have read the first post carefully. I don't like this hostile attitude.musher0 wrote:Now he tells us...
(...)
reaction that's ever so slightly non-standard. Jesus!
You're reading it with the wrong tone. It's not hostile. It's supposed to be
ironic, a "taking-the-whole-thing-with-a-grain-of-salt-when-things-
don't-go-your-way" attitude. Don't you ever laugh at yourself? Don't you
have a sister or friends that tease you?
As I said to mavrothal: practice Cartesian Doubt, my friend, with yourself
as well as in your computer science work. Take a step back, by golly.
Don't you see I'm trying to put your suggestion of using woof-CE in
practice? Ok, I'm the anxious type, and humour is my way of letting off
steam. This woof process is making me extremely anxious, as I'd really
like to succeed at it.
Sorry if my way of dealing with anxiety offends some people, but I can't
help it, my personality is like that. Love it or leave it. I'm the first victim
of my personality, remember that.
But there's a wide gap between teasing and hostility. Phew.
I actually like you, your generous attitude, your selflessness, and the
work you do for Puppy.
BFN.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Iguleder and others:
Are there particular builds that you would like to see made? For me, it almost doesn't matter which one I make. Slacko Version, Ubuntu, Debian, no matter.
As long as I can get MPlayer, LibreOffice, a Chromium based browser, Roxterm, Photorec/Testdisk and my handmade scripts to work, any version is fine with me. Oh, and let's not forget the never present Zaxxon. Small and works on every pup.
Are there particular builds that you would like to see made? For me, it almost doesn't matter which one I make. Slacko Version, Ubuntu, Debian, no matter.
As long as I can get MPlayer, LibreOffice, a Chromium based browser, Roxterm, Photorec/Testdisk and my handmade scripts to work, any version is fine with me. Oh, and let's not forget the never present Zaxxon. Small and works on every pup.
Hello again.
FWIW:
I decided not to make a tahrPup because there are already 2-3 of them.
What is the point of repeating what has already been done, eh? With the
chance of failing at it, too?
There is no Jessie Puppy yet. There's is a JessieDog by saintless & Co, but
as saintless himself has explained, it's not really a Puppy.
BFN.
musher0
FWIW:
I decided not to make a tahrPup because there are already 2-3 of them.
What is the point of repeating what has already been done, eh? With the
chance of failing at it, too?
There is no Jessie Puppy yet. There's is a JessieDog by saintless & Co, but
as saintless himself has explained, it's not really a Puppy.
BFN.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
I decided to go with the Tahr just as a first test run....
Ted Dog, it's gonna take me a while to get the Zaxxon up there. Dropbox not working on my QU so I'll have to wait while I'm in Woof-CE. By the AM for sure.
Zaxxon is on this page:
http://www.smokey01.com/bruceb/pets_n_stuff.html
ctrl-f to find it....
It works on every puppy that I ever used since Precise, at least....
Back to business: I gather moving the whole project to RAM will save significant time. So that will be my next step.
Also, do the 4babybuild and 4quirkybuild work? How would they be incorporated into the initial post?
Ted Dog, it's gonna take me a while to get the Zaxxon up there. Dropbox not working on my QU so I'll have to wait while I'm in Woof-CE. By the AM for sure.
Zaxxon is on this page:
http://www.smokey01.com/bruceb/pets_n_stuff.html
ctrl-f to find it....
It works on every puppy that I ever used since Precise, at least....
Back to business: I gather moving the whole project to RAM will save significant time. So that will be my next step.
Also, do the 4babybuild and 4quirkybuild work? How would they be incorporated into the initial post?
Hello, all.
Here is a short interim report on the woof-CE build of "Puduan-6.0":
to a dir, added the devx to it and used peasydisc to re-create an iso. I also used
peasydisc to burn the new iso to a DVD+RW..
The iso booted fine up to the X. I tested both xorgwizard options (modesetting and
radeon) one after the other, but still couldn't access the X desktop with the xwin jwm
command.
I hope the other testers have better luck.
Have a great week-end!
musher0 out.
Here is a short interim report on the woof-CE build of "Puduan-6.0":
Pburn reporting that the original iso was data only (i.e. non-bootable), I unpacked ittotal 319M # Note: For the entire directory.
_______________ # The size of the original iso is only 73 Mb.
-rw-r--r-- 1 159M oct 3 20:49 puduan-6.0.0+devx.iso
# the new iso with devx
drwxr-xr-x 2 4,0K oct 3 20:45 puduan-6.0.0.iso_extracted
-rw-r--r-- 1 86M oct 3 19:51 devx_puduan_6.0.0.sfs
# devx bigger than the iso, actually.
-rw-r--r-- 1 56 oct 3 19:51 devx_puduan_6.0.0.sfs.md5.txt
-rw-r--r-- 1 51 oct 3 19:26 puduan-6.0.0.iso.md5.txt
-rw-r--r-- 1 73M oct 3 19:26 puduan-6.0.0-non.iso # the old iso
to a dir, added the devx to it and used peasydisc to re-create an iso. I also used
peasydisc to burn the new iso to a DVD+RW..
The iso booted fine up to the X. I tested both xorgwizard options (modesetting and
radeon) one after the other, but still couldn't access the X desktop with the xwin jwm
command.
I hope the other testers have better luck.
Have a great week-end!
musher0 out.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Just started reading Pro GIT by Chacon & Straub . If I learned ANYTHING from its early reading it is "Throw everything I ever knew about the old CVS and SVM out, and start over for GIT". The old CVS/SVM contribute almost NOTHING, except a knowledge of how they work. GIT accomplishes the very same objective in a much improved manner for the way elements should be maintained.
GIT, I can see is an advancement and TOTALLY unique in both concept and operation. It is unparalleled in comparison to the old.
One creditable brief on GIT is found here.
Hope this info is helpful to anyone.
GIT, I can see is an advancement and TOTALLY unique in both concept and operation. It is unparalleled in comparison to the old.
One creditable brief on GIT is found here.
Hope this info is helpful to anyone.
Last edited by gcmartin on Tue 20 Oct 2015, 15:11, edited 2 times in total.
My first go with Trusty Tahr not very impressive. Issues with the initial pop-up to choose network and setup. Also, Frisbee didn't seem to install or install properly. Screen also cut-off on top. I didn't take notes on this one. It was my first go so certainly subject to user error. Anyway, moving forward....
Good on you slavvo67 for having a go. (Of course you too musher0 )
At least with some feedback we can attempt to fix bugs.
Cheers
At least with some feedback we can attempt to fix bugs.
Cheers
Puppy Linux Blog - contact me for access
Thanks for the thanks, Mick.
Browsing the web with no particular aim, I found this, which I think could be
a motto for this thread. Or not!
"Every dog thinks her puppies are the cutest." (American proverb)
From: http://oaks.nvg.org/amea.html
TWYL.
musher0
Browsing the web with no particular aim, I found this, which I think could be
a motto for this thread. Or not!
"Every dog thinks her puppies are the cutest." (American proverb)
From: http://oaks.nvg.org/amea.html
TWYL.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
musher0 wrote:Hello again.
At the build iso question, I answered "(space)ENTER", but it still went
ahead with burning. Although the script said: "type any character then
Enter if you don't want to burn."
I thought (space) was a valid ASCII character!
Luckily I'm a character too, and my dvd was unusable.
(Don't look for any relevance, there isn't any!)
The script also warned me that Bacon dev was not in the devx, with some
instructions how to include it. A bit late now, I'd say! while it's
squishing the devx.
This is lots of fun!
musher0
I've never been able to print a space (underline is mine)./3builddistro wrote:Would you like to burn it to a CD?
ENTER only for yes, or any printable char then ENTER not to:
Puppy Linux Blog - contact me for access
Yeah, same category as one-hand clapping, I guess. Sorry I misread.
(Edit: and a transparent icon.)
Still, a (space) character does exist as Dec 32, Hx 20, etc. (please see
top of 2nd column, here).
(Edit: and a transparent icon.)
Still, a (space) character does exist as Dec 32, Hx 20, etc. (please see
top of 2nd column, here).
Last edited by musher0 on Sun 04 Oct 2015, 17:09, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)