Slow but steady progress adding to T2

Comments
I was logging progress here:
http://bkhome.org/news/?viewDetailed=00134

However, decided to start a new thread.

Some more:

guess_fs
gview
gwhere


gview home page:
http://gview.sourceforge.net/

gwhere home page:
http://www.gwhere.org/

Gwhere needed a lot of TLC to compile. Feasible as it is written in C -- if it had been written in C++ it would have been a hopeless case.

...that's because the C++ developers shift the goal posts, unlike C that basically remains the same over the years.

I wonder if anyone uses these apps? I have put gview and gwhere into all my pups, for years and years.
Gwhere is a nice concept, though I never used it myself. It kind of filled a niche, so I always put it in.
Posted on 18 Dec 2014, 21:20 - Categories: Quirky


Gpptp v2.0 in T2

Comments
I announced recently the work that Puppy Forum member jafadmin has done, developing Gpptp, which is PPTP VPN client:
http://bkhome.org/news/?viewDetailed=00104

The PET package has two binary executables in it. I have taken the sources out to a separate package, named 'gpptp-2.0' and the compiled binary pkg will have the same name.
The PET, without the binaries, is now named 'gpptp-noarch-2.0'.

The latter will be uploaded to the Quirky noarch PET repo soon. It will be here:
http://distro.ibiblio.org/quirky/quirky6/noarch/packages/pet_packages-noarch/

The former will be uploaded to the April sources repo soon. That is here, not complete yet:
http://distro.ibiblio.org/quirky/quirky6/sources/t2/april/

The binary packages created by T2 will be uploaded here, but there is nothing there yet:
http://distro.ibiblio.org/quirky/quirky6/x86/packages/t2/april/
Posted on 17 Dec 2014, 23:09 - Categories: Quirky


Continuing to import into T2

Comments
I am working intensely on this. Days are rolling past, I will keep going until they are all in.

I am logging progress in this blog thread:

http://bkhome.org/news/?viewDetailed=00134
Posted on 17 Dec 2014, 16:59 - Categories: Quirky


pup-tools in T2

Comments
I posted about compiling BaCon in T2:
http://bkhome.org/news/?viewDetailed=00135

That allowed the next step, which is to compile all of my utilities written in BaCon.

In woofQ I have centralised all compilable sources, that are inside woofQ. These are inside a directory named 'source', and there is a script that will construct a source tarball for T2, named pup-tools-<date>.tar.gz.

This script also asks for logos and name of the distro. So, for the example of 'welcome1stboot', the first-boot welcome window, which is actually welcome1stboot.bac, written in BaCon, this is now customisable.
In Quirky, welcome1stboot displays the Quirky logo and text like this:

" Welcome, this is the first time that you have started Quirky"

The logo can be changed to whatever you want, and the name "Quirky" replaced with whatever you want.

So, the generated source tarball can be supplied to T2, and T2 will generate a binary package, with the same name, pup-tools-<date>.tar.bz2.

'pup-tools' needs to be in the package-list of your target-build in woof. Here is the current content of the binary pkg:

/bin/vercmp
/usr/local/petget/debdb2pupdb
/usr/local/petget/find_cat
/usr/local/pup_event/pup_event_frontend_d
/usr/local/pup_event/pup_event_ipc
/usr/local/simple_network_setup/proxy-setup
/usr/sbin/getcurpos
/usr/sbin/pngoverlay
/usr/sbin/popup
/usr/sbin/printcols
/usr/sbin/welcome1stboot
/usr/share/doc/nls/proxy-setup/proxy-setup.pot
/usr/share/doc/nls/welcome1stboot/welcome1stboot.pot


Most of these are written in BaCon. Only vercmp, getcurpos and printcols are written in C. I compiled vercmp and printcols statically with dielibc.
Posted on 16 Dec 2014, 22:35 - Categories: Quirky


BaCon in T2

Comments
I am firing on all eight cylinders today!
What's left of it anyway -- it is now ten minutes to midnight.

I have been logging my work importing source packages into T2:
http://bkhome.org/news/?viewDetailed=00134

A major hurdle has now been jumped. I needed to compile BaCon in T2, as the BaCon compiler is needed for many utilities used in the puplets.

It was not that straightforward. I downloaded the latest version, 3.0.2, from the home site:
http://www.basic-converter.org/

...and compiled it in T2.

I then downloaded several individual files and created a tarball 'bacon_runtime-3.0.2.tar.bz2'.
As the name suggests, this mostly has runtime components, in particular the 'hug.so' shared library and 'bacon.lang' and 'bacon.vim' text editor syntax-highlighter files.

hug.so is a shared library that BaCon applications that use the HUG high-level GTK GUI can use to make their executable file smaller.
It has to be compiled and installed to /usr/lib/hug.so

So I imported 'bacon_runtime' into T2, and created custom compile and install code.

Then I had to create a package template in woofQ, to set things up properly, such as register the syntax-highlighters with their appropriate editors.

The great thing about all of this, is what has been in my brain, and documented in an ad-hoc manner, or in places you can't find, is now formalised in definite steps in T2.
Posted on 15 Dec 2014, 23:51 - Categories: Quirky


Pages: [1] [2] [3] [4] [5] ...