Packages Repository

[ZDevil]

Just checked the 4.1/arm packages feeds. py-cairo is also missing there ...

[jpmatrix]

I wonder if the feed http://www.planetofidiots.com/pub/OpenBSD/...ackages/zaurus/ is still working. It is not browsable.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

apparently not
anyway, i'm beginning to compile some packages :

[a href=\"http://matrixmen.free.fr/zaurus/openbsd/pkg4.1/]http://matrixmen.free.fr/zaurus/openbsd/pkg4.1/[/url]

more will come later
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

updated & new url:
[a href=\"http://matrixmen.free.fr/zaurus/openbsd/pkg4.1/all/]http://matrixmen.free.fr/zaurus/openbsd/pkg4.1/all/[/url]

ftped with mc under OpenBSD Zaurus

[ZDevil]

Cool. Thanks a lot. Now go installing everything.
Will hop on the compiling bandwagon once i receive my ambicom wifi cf.  

[ZDevil]

Hey, just compile emacs-unicode2 (emacs 23.0.0.1) on board!
Compilation feels faster than using the zgcc toolchain on pdaX. Maybe my illusion because i was doing it on SD card under pdaX    
This is gonna be my virgin port for OpenBSD/Zaurus.  

Next: Chinese inputmethod, xchm, and a few roguelikes.

[ZDevil]

A quick question about compilation flags:

It's suggested that we add -mcpu=xscale as optimizing CFLAGS/CPPFLAGS.
Then how about other optimization options, such as -O2, which is the default when compiling apps for linux?  I've searched the web for a while and don't find anything discussing this directly. Thanks.  

[ZDevil]

(Disclaimer: The following report is true as of 14 May 2007; things may change when a more complete and updated feed comes up.)

So far, I've come across these three "unofficial" user feeds (well, when will there be an official package feed for Zaurus? ):

http://www5.autistici.org/c0de/obsd/pkg4.1/
http://matrixmen.free.fr/zaurus/openbsd/pkg4.1/all/
http://www.planetofidiots.com/pub/OpenBSD/...ackages/zaurus/ (it's back with more updated packages)

First of all, a millions thanks to the contributors for your hard efforts to make these ports ready for OpenBSD/Zaurus!    

The packages in the first two seem to largely get along well (except a few), but the third one has newer stuff that don't seem to be compatible with many packages in the first two feeds, notably things dependent on or shared with atk, glib and gtk.

If you so happened to have installed things from all the three feeds (like what i did earlier on ...   I have to admit that i am kinda greedy ... ),
then you should first use pkg_delete -ci PACKAGENAME to uninstall the conflicting packages, and those that are associated with them -- say YES when asked whether to delete all those other associated packages.
Then try to install the ones that fit.
But when installing the suitable ones, chances are that installation will run into errors saying some conflicting libraries and files are already present. It takes a while for a list of these files to come up.
Look at the list and manually delete all the unfitting libs.
Then install the desired packages again. That should do the trick (at least to a large extent).

I have to admit that this is a kinda stupid way. Since there is no port trees for the unofficial packages, so i have to do trial and error to find out the (in)compatibilities among the packages.

I've been reinstalling and uninstalling for a few times to ensure things are in harmony.
It seems i have to taken out the newer atk-1.18.0p0.tgz, glib2-2.12.11p0.tgz and gtk+2-2.10.10.tgz out from the third feed and keep using the older ones from the first two feeds if i want to have a maximal set of working packages in the system.

For instance, firefox is missing in the third feed (for now perhaps?) and it can only work with the older libs from the first two feeds.

I believe having ready made packages is nice, which can save a huge chuck of time on the users' part. Yet things would be much smoother if there is one central (official) feed so that things are updated uniformly and consistently. But correct me if i am wrong.

[ZDevil]

I have already started porting apps not found in the three feeds.

The native toolchain which is part of the system installation works like a charm.  

So far I have finished a tiny set: emacs-unicode2, icewm 1.30 (latest), SDL, SDL-mixer, SDL-image, SDL-ttf, SDL-net, and a few others are coming.  

Now thinking of making the builds into PKG, but still cannot find where to start to package things up after reading http://www.openbsd.org/porting.html and iamsmith's post about ports and packages in this forum.  Can someone drop me a pointer so that i can go check it out myself?  

It would be great if there is a short demo/example of how to package. Thanks in advance!

I don't have my own free web space to host the builds, but i am more than happy to send mine to any of those feeds, just as what i can do to contribute for now.  Anyone interested?


PS I find that the first feeds I mention in the previous largely follow the content of the arm feeds, plus more nice stuff (such as firefox).

[mathemajikian]

Can someone drop me a pointer so that i can go check it out myself?

Here's a simple example:

# cd /usr/openbsdports/sysutils/colorls
# more Makefile
 

Code: [Select]

$OpenBSD: Makefile,v 1.12 2006/10/21 09:42:32 naddy Exp $

COMMENT=        "ls that can use color to display file attributes"

DISTNAME=       ls-3.9
PKGNAME=        color${DISTNAME}
CATEGORIES=     sysutils

MAINTAINER=     Christian Weisgerber

# BSD
PERMIT_PACKAGE_CDROM=   Yes
PERMIT_PACKAGE_FTP=     Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP=   Yes

MASTER_SITES=   http://sites.inka.de/~mips/unix/distfiles/

WRKDIST=        ${WRKDIR}/ls   <---- this is the build directory in /usr/openbsdports/sysutils/colorls/w-colorls-3.9
NO_REGRESS=     Yes

pre-patch:
        cp ${WRKSRC}/ls.1 ${WRKSRC}/colorls.1

.include
# cd /usr/openbsdports/sysutils/colorls/pkg
# more PLIST

Code: [Select]

@comment $OpenBSD: PLIST,v 1.2 2005/09/05 11:55:47 espie Exp $
bin/colorls
@man man/cat1/colorls.0
You should be able to figure it our from here.

[jpmatrix]

I don't have my own free web space to host the builds, but i am more than happy to send mine to any of those feeds, just as what i can do to contribute for now.  Anyone interested?

i can give you some space on my website if you want, i think i've 10GB.
but you'll have to wait for a week as i'm on holidays until may 23

[ZDevil]

Thanks, mathemajikian. This seems a very good starting point. Does it mean you have to write the Makefiles and PLIST by hand yourself? And how do you package up the builds into the package .tgz ? I have taken a brief look into the file structure of some sample packages, but I just want to be sure what I do is the standard way of porting.    

To jpmatrix: thanks for offering to host the packages! Coincidentally I will be away for a week from 24 May.   Will take this couple of weeks to explore and do experiments.  

Now building xchm and its dependencies (wxGTK, xmlpc++, chmlib) ...

[mathemajikian]

Thanks, mathemajikian. This seems a very good starting point. Does it mean you have to write the Makefiles and PLIST by hand yourself? And how do you package up the builds into the package .tgz ?

If you are trying to create a package for a port which isn't already in the ports collection, then you'll have to generate the Makefile and PLIST plus any other misc files. However, if you are just building ports which are already in the ports collection then:

# cd /usr/ports/packages/arm/all
# ls

and you'll see that the packages have been created for you during the normal make install process. I'm assuming you knew this.........

[ZDevil]

Thanks, mathemajikian. This seems a very good starting point. Does it mean you have to write the Makefiles and PLIST by hand yourself? And how do you package up the builds into the package .tgz ?

If you are trying to create a package for a port which isn't already in the ports collection, then you'll have to generate the Makefile and PLIST plus any other misc files. However, if you are just building ports which are already in the ports collection then:

# cd /usr/ports/packages/arm/all
# ls

and you'll see that the packages have been created for you during the normal make install process. I'm assuming you knew this.........
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161328\"][{POST_SNAPBACK}][/a][/div]

Frankly, I didn't know this before, because I am still waiting for my CF wifi to make full use of the Port system. For now I am compiling locally from downloaded sources.  

[jpmatrix]

However, if you are just building ports which are already in the ports collection then:

# cd /usr/ports/packages/arm/all
# ls

and you'll see that the packages have been created for you during the normal make install process. I'm assuming you knew this.........
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161328\"][{POST_SNAPBACK}][/a][/div]

by the way, can you explain us (openbsd newbie), why there are 3 directories (all, cdrom, ftp) with the same .tgz in them and can we safely delete some to make some room ?

[mathemajikian]

Frankly, I didn't know this before, because I am still waiting for my CF wifi to make full use of the Port system. For now I am compiling locally from downloaded sources.   

Well here's another trick. If you look at the Makefile for www/links+ you'll see

VER=            2.1pre28
DISTNAME=       links-${VER}
MASTER_SITES=   ${HOMEPAGE}download/
HOMEPAGE=       http://links.twibright.com/

If you download links-2.1pre28.tar.gz from  http://links.twibright.com/download/links-2.1pre28.tar.gz
and copy it to /usr/ports/distfiles/ then you'll be able to build links+ from the ports collection assuming that all other build dependencies have been met. If your missing a build dependency then analyze the missing dependencies Makefile as shown above and copy the missing dependencies downloaded tar.gz to /usr/ports/distfiles/. Continue this process until all the build dependencies have been met and you'll end up with the port along with it's dependencies being built in the ports tree.

[mathemajikian]

By the way, can you explain us (openbsd newbies), why there are 3 directories (all, cdrom, ftp) with the same .tgz in them

These copies are generated because it is told to do so in the Makefile:
 

Code: [Select]

PERMIT_PACKAGE_CDROM=   Yes
PERMIT_PACKAGE_FTP=     Yes

Can we safely delete some to make some room ?

Yes, you can safely delete them from arm/cdrom and arm/ftp. Just keep the original in arm/all.