Hi:

Based on these changes, I've updated the techbase page to reflect the
way *I*'ve used to create and publish IPS packages:

http://techbase.kde.org/index.php?title=Projects/KDE_on_Solaris/OpenSolaris#Creating_KDE4_IPS_packages

I hope it'll be useful for someone (and everyone is free to
comment/improve/whatever it).


Kind regards.


On Fri, Jan 16, 2009 at 04:31, Adriaan de Groot <groot at kde.org> wrote:
> On Tuesday 13 January 2009 10:45:23 Jan Hnatek wrote:
>> please see the response I got for the same question:
>> http://mail.opensolaris.org/pipermail/kde-discuss/2008-December/001808.html
>
>
> I hope that was the one where I wrote that the combination of NAT + NAT +
> VirtualBox was too much for large transfers and that I was switching the
> machine off. It's possible to compile IPS packages and publish them yourself;
> typically you would go one by one and run 'make ips-<package>' in the right
> install order; you will have to read the specfiles to find that order, though.
> So something like:
>
>        make check-version
>        make ips-FOSShier
>        make ips-FOSSgiflib
>        make ips-FOSSstdcxx
>        make ips-FOSSicu4c
>        make ips-FOSSboost
>        ...
>
> One tool you can use to find out what the direct or indirect dependencies are
> for a package is 'show-missing' which is a target in tools/Makefile.admin:
>
>        make -f tools/Makefile.admin show-missing TARGET=KDElibs
>
> This will list all the packages you need to install before the given TARGET;
> if it lists none (or just TARGET itself) then you can run 'make ips-TARGET' to
> build it now. The process uses IPS_ARGS from Makefile.config to configure
> things like the -s arguments to pkgsend.
>
>> homerun wrote:
>> > How about making these pkg's available
>> > in contrib repo ,  http://pkg.opensolaris.org/contrib
>> > under "Desktop ( KDE4 )" selection.
>> > Same way that there is now "Desktop (GNOME)"
>
> Yes. But I'm not in a position to do it now, and I don't feel like jumping
> through the contrib/ hoops myself. You can do it, though: the tools are all
> there, the specfiles meet the criteria set out for contrib (or pending/ - i
> forget which). Only issue might be the license files, which that ips-create-
> manifest tool sticks together based on the available license information.
> There seem to be some issues on that. I started posting to sw-porters-discuss
> before leaving on my current trip, do check those archives as well.

-- 
Pablo M?ndez Hern?ndez

Reply via email to