Packages Repository, fluxbox - idesk - etc Options

[zogs]

Hi
if you want fluxbox, idesk, irssi or other packages precompiled for your OepnBSD 4.0 in your zaurus
you can put your PKG_PATH in http://www5.autistici.org/c0de/obsd/pkg4.0/

here if you want a howto for setting some pkg_path for your pkg_add [simple howto for setting PKG_PATH]

sorry my english I'm drinking

[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.........

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.

[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.

[ZDevil]

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.

A new question: What if the program is missing in the current ports collection? Does that mean there will be no dependency check and no BSD Makefile and Plist will be generated?