Page 1 of 4
racket
Posted: 19. Sep 2012, 17:21
by mimosa
This is nearly finished in the sense that the build works. However one thing I'm stuck with is the menu icon.
I can see from the instructions where to put it, but I'm not sure where to get it from. Should I make one myself? What size should it be?
http://people.salixos.org/mimosa/packag ... 3/SLKBUILD
Re: [WIP]racket
Posted: 19. Sep 2012, 23:42
by laprjns
mimosa wrote:but I'm not sure where to get it from.
/racket-5.3/collects/icons/. I think the plt-32x32.png and plt-48x48.png are the only ones you need to install.
Re: [WIP]racket
Posted: 19. Sep 2012, 23:48
by mimosa
That's very kind of you, laprjns
- I'll have a look at those in the morning.
Needless to say, I searched the source, but to me it looked like a haystack.
Re: [WIP]racket
Posted: 20. Sep 2012, 09:58
by laprjns
mimosa wrote:That's very kind of you, laprjns
but to me it looked like a haystack.
yeah, so I cheated and look at the arch PKGBUILD
Re: [WIP]racket
Posted: 20. Sep 2012, 10:08
by mimosa
I cheated and looked at the Arch PKGBUILD
That still leaves the problem of how they (or whoever packaged it first) worked it out.
I hope to put the finishing touches to this today (after I head over to Arch and see how they did it)
Re: [WIP]racket
Posted: 20. Sep 2012, 10:34
by laprjns
I use this as my starting point template
Code: Select all
# lets deal with the icons
for size in 10 22 24 32 48 64 128
do
mkdir -p $startdir/pkg/usr/share/icons/hicolor/${size}x${size}/apps/
cp -rf $startdir/src/$pkgname-$pkgver/share/agender${size}.png $startdir/pkg/usr/share/icons/hicolor/${size}x${size}/apps/
done
and make appropriate adjustments required by the package.
So in this case I would end up with this:
Code: Select all
# lets deal with the icons
for size in 32 48
do
mkdir -p $startdir/pkg/usr/share/icons/hicolor/${size}x${size}/apps/
cp -rf $startdir/src/$pkgname-$pkgver/collects/icons/plt-${size}.png $startdir/pkg/usr/share/icons/hicolor/${size}x${size}/apps/
done
And for full disclosure, I stole this from one of gapan's SLBUILDs back a few years ago.
Re: [WIP]racket
Posted: 20. Sep 2012, 13:59
by mimosa
The "docs" line in the SLKBUILD includes files such as README. Where are these searched for? In this case, there is a file "COPYING.txt" (basically the licence) hidden away in a subdirectory doc/release-notes. Do I need to do anything special to make sure this is included - or should I upload it myself and include it in the "source" line along with the .desktop file and any others?
Re: [WIP]racket
Posted: 21. Sep 2012, 15:21
by mimosa
man SLKBUILD answers my question about docs:
Don't worry
about specifiying any path or the case of the docs because slkbuild does a case insensitive recur‐
sive search for whatever you provide.
However that leads to a related question: what happens when, say, the top directory contains a README file, but so do one or more directories beneath it? That is actually the case here, to a spectacular extent:
Code: Select all
vanilla[racket-5.3]$ find ./ -name README
./README
./collects/2htdp/utest/README
./collects/mzscheme/examples/README
./collects/tests/racket/README
./collects/tests/framework/README
./collects/tests/gracket/README
./collects/tests/mzcom/README
./collects/web-server/compat/0/README
./collects/web-server/compat/README
./collects/redex/examples/r6rs/README
./collects/redex/examples/README
./collects/defaults/README
./collects/frtime/demos/README
./collects/slatex/README
./src/foreign/libffi/README
./src/foreign/README
./src/racket/gc2/README
./src/racket/gc/doc/README
./src/racket/README
./src/racket/src/lightning/README
./src/racket/src/gmp/README
./src/racket/sgc/README
./src/gracket/README
./src/README
This last file contains installation info, the first one points to the licence.
Re: [WIP]racket
Posted: 21. Sep 2012, 16:23
by gapan
In that case, one of them goes in. You'll have to stop using the docs array in that case and process them manually.
Re: [WIP]racket
Posted: 21. Sep 2012, 18:41
by mimosa
What criterion should I use to decide what to include? Most of those are introductions to the files in a particular directory, and won't even make sense in /usr/doc/$pkgname-$pkgver. On the other hand, racket is very well documented internally.
My inclination is to omit the README in the top level (which just points to COPYING.txt one level below for licence information), include the latter but renamed as LICENCE, and the final README which contains the normal installation instructions; as well as any other ones like authors, todo.