helidelinux-devel

[Helidelinux-devel] bpm spec files get a new tag, and emacs sizes

[Bennett T. <be...@ra...>]

Still haven't gotten around to the major todos (custom cpio writer
to give control over perms, removing need for bpmpkgfix; then
automated dependency analysis), but I just decided to add an
optional tag somewhat in the flavour of rpm's "Group". I call it
"isa", and give it a list of keywords (whose order has no intended
meaning). I just used it to tag all the emacses I've built, since
I went on a binge, and with the tags in place it was a couple of
simple shell loops to compute:

     12938   e3em
     56296   ee
     56604   emt
     86816   elle
    133144   ved
    158136   jove
    222636   microemacs
    281556   zile
    420648   jed

Those are file sizes in bytes for -Os -static -s compilations
against uClibc.

-Bennett

Re: [Helidelinux-devel] bpm spec files get a new tag, and emacs sizes

[Rolf V. <rol...@he...>]

It is so nice to be free from schemas and to be able to
add fields on the fly :-).

Rolf.

Bennett Todd wrote:
> Still haven't gotten around to the major todos (custom cpio writer
> to give control over perms, removing need for bpmpkgfix; then
> automated dependency analysis), but I just decided to add an
> optional tag somewhat in the flavour of rpm's "Group". I call it
> "isa", and give it a list of keywords (whose order has no intended
> meaning). I just used it to tag all the emacses I've built, since
> I went on a binge, and with the tags in place it was a couple of
> simple shell loops to compute:
> 
>      12938   e3em
>      56296   ee
>      56604   emt
>      86816   elle
>     133144   ved
>     158136   jove
>     222636   microemacs
>     281556   zile
>     420648   jed
> 
> Those are file sizes in bytes for -Os -static -s compilations
> against uClibc.
> 
> -Bennett

Re: [Helidelinux-devel] bpm spec files get a new tag, and emacs sizes

[Bennett T. <be...@ra...>]

2004-05-13T08:50:23 Rolf Veen:
> It is so nice to be free from schemas and to be able to
> add fields on the fly :-).

For _sure_, that freedom has been something I've been adamant on
since well before you came strolling into my life and lured me away
to this OGDL thingie:-).

Before I was doing OGDL, I was specifying my packaging spec files in
Lua <URL:http://www.lua.org/>. Looked a _lot_ like my current OGDL
spec files, only with a bit more typographic noise. Instead of:

    pkg tla-1.2

    url http://ftp.gnu.org/gnu/gnu-arch/tla-1.2.tar.gz

    build \
        tar xzf tla-1.2.tar.gz
        cd tla-1.2
        cd src
        mkdir =build
        cd =build
        ../configure --prefix=/usr --destdir=$BPM_ROOT --with-cc='gcc -Os -s -static'
        make
        make test
        make install

it would have been:

    pkg = "tla-1.2";

    url = "http://ftp.gnu.org/gnu/gnu-arch/tla-1.2.tar.gz";

    build = [[
        tar xzf tla-1.2.tar.gz
        cd tla-1.2
        cd src
        mkdir =build
        cd =build
        ../configure --prefix=/usr --destdir=$BPM_ROOT --with-cc='gcc -Os -s -static'
        make
        make test
        make install
    ]];

I like OGDL, no question it's still cleaner and sweeter, but the Lua
version didn't half suck:-). And it was every bit as open-ended and
schema-free.

-Bennett