|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
||||
Sorry wanted to add these as things I've read but couldn't till now (post 5+):
http://www.openbsd.org/faq/faq5.html http://www.openbsd.org/faq/ports/ http://www.openbsd.org/faq/ports/differences.html#Fetch http://www.openbsd.org/cgi-bin/man.c...=1&format=html Would I be correct in assuming that in order to build a port I would need to run: Code:
pkg_create <source.tar.gz> |
|
||||
Off. The pkg_create(1) application is normally used under the covers by the porting infrastructure during make(1) with the package target, and almost never by a port developer.
You've missed FAQ 15 -- or you read it and were confused -- it wasn't in your list of documents you've reviewed. There's great guidance there. In order to "use" the ports tree, you must first obtain a ports tree that is synced to the flavor of the OS you are using. (You can only mix and match -stable and -release, as they use the same underlying libraries.) For -release, you can download and unpack the ports tarball. For -stable, you must use cvs(1). For -current, there is a daily tarball but cvs may be more convenient. Note: There is usually little difference between the -release and -stable ports trees; for the last several years there hasn't been sufficient resources to develop -stable ports except when there has been a security issue with some port. |
|
|||
"Ports" refers to the source code + Makefile infrastructure needed to build third-party applications sanctioned by the OpenBSD project. "Packages" are the result of building ports.
Most users of OpenBSD should only be concerned about installing packages which is covered in Section 15 of the project's official FAQ. Rarely should general users need to build from the ports tree. Repeating, the build process builds packages before installation. These are the same packages available on the mirror sites, so unless there is a specific reason to build, most users should be installing from the mirror sites as opposed to building themselves. Quote:
Quote:
The FAQ is the single best starting point for newcomers to OpenBSD. You will save yourself significant time & aggravation by taking the time now to study its contents. |
|
||||
Ok I checked FAQ15 out.
Got the "ports" tree installed by doing this according to the guide: {I used /home as there was more space in it then /tmp where the tar.gz wouldn't fit} Code:
cd /home tar -C /usr -xzf ports.tar.gz # chgrp -R wsrc /usr/ports # find /usr/ports -type d -exec chmod g+w {} \; echo "USE_SYSTRACE=Yes" > /etc/mk.conf $ cd /usr/ports $ make search key=rsnapshot So now it should work like how I'm used to! However, a quick question is - if I want to install a package not in the ports tree can I still build it as though it was a port? eg. download the source into /usr/ports dir then run "make install clean" after going to /usr/ports/<source> |
|
||||
No, sparky.
The ports tree contains infrastructure for building ports, not the ports' source code, and each leaf of the tree contains a series of OpenBSD-specific files/folders specific to that port, such as a Makefile, a distinfo file, and packing lists and installation messages in pkg/*, as well as optional patches/* or files/* when needed for OpenBSD uniquely. Your choice with custom applications is to either:
Please read FAQ 15's sections on ports very carefully. Last edited by jggimi; 12th March 2012 at 06:54 PM. Reason: typo, clarity |
|
||||
Thanks a lot jggimi!
I understand now, at least better how things work. I kinda had a secret agenda to be able to get LCDproc working in OpenBSD but since I was already running it on **other** platforms I was already signed up to the mailling list meaning that a quick question as to why the software wasn't compiling got me the response that I needed to use the CVS version. Now all is fine and I have managed to compile my first piece of software without errors on OpenBSD. Many thanks for the support. Still a loooooong way to go though as it's a steep learning curve! |
|
||||
Yes, it's a learning curve. But I'll beat the horse once more ... I thought I heard it sigh.
The FAQ is the only official "HOWTO" collection. You'll save yourself lots of time and shorten that learning curve by spending time with it. As far as LCDProc goes, while I know nothing about it, I know that Edd Barrett was developing a port for it in November: http://marc.info/?t=132173736200033&r=1&w=2 |
|
||||
Quote:
Quote:
So finally when I come to buliding my Cisco killer 10GbE router it should be out. I like LCD panels as they're a good way of getting info without typing and they look pretty in racks/general! |
|
|||
Quote:
http://www.openbsd.org/cgi-bin/cvswe...dproc/Makefile It is already officially available to users of -current. However, you should note where the OPENBSD_5_1_BASE CVS tag is placed (as this denotes what will be available with OpenBSD 5.1-release). The very latest lcdproc check-in made two weeks ago is newer than the 5.1 CVS tag; thus, this particular check-in is only available to -current users. Is this check-in important? I don't know as I don't use lcdproc. The point here is that development of the port is actively on-going. If you are confused by the different flavors of OpenBSD: -release, -stable, & -current, study Section 5.1 of the FAQ. Last edited by ocicat; 13th March 2012 at 01:39 AM. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
FreeBSD Complete ports thaw after ports freeze for 7.3 Release | J65nko | News | 0 | 24th March 2010 11:46 PM |
PF Configuration for newbie | slakic | OpenBSD Security | 1 | 20th August 2009 02:35 PM |
UML tools | bichumo | Programming | 2 | 12th September 2008 02:23 PM |
Newbie NAT problem | TiN-MAN | FreeBSD Installation and Upgrading | 2 | 26th June 2008 06:42 AM |
Benchmarking Tools | JMJ_coder | NetBSD General | 8 | 16th June 2008 10:42 PM |