[BACK]Return to README CVS log [TXT][DIR] Up to [local] / ports / base
File: [local] / ports / base / Attic / README (download)

Revision 1.1.1.1 (vendor branch), Thu Nov 1 09:58:05 2012 UTC (11 years, 7 months ago) by espie
Branch: espie
CVS Tags: ports, OPENBSD_6_2_BASE, OPENBSD_6_2, OPENBSD_6_1_BASE, OPENBSD_6_1, OPENBSD_6_0_BASE, OPENBSD_6_0, OPENBSD_5_9_BASE, OPENBSD_5_9, OPENBSD_5_8_BASE, OPENBSD_5_8, OPENBSD_5_7_BASE, OPENBSD_5_7, OPENBSD_5_6_BASE, OPENBSD_5_6, OPENBSD_5_5_BASE, OPENBSD_5_5, OPENBSD_5_4_BASE, OPENBSD_5_4, OPENBSD_5_3_BASE, OPENBSD_5_3
Changes since 1.1: +0 -0 lines 

experimental work: build xenocara components as "packages" and hook them
into dpb.
not 100% ready yet, committed to keep working in tree.

# $OpenBSD: README,v 1.1.1.1 2012/11/01 09:58:05 espie Exp $
This is a set of experimental ports to build xenocara as components
They reach out into ${XSRCDIR} to get access to the component.

Each package is fake ! the real tarball is built under
${PACKAGE_REPOSITORY}/${ARCH}/components

the "package" will install stuff under /usr/local/libdata/base/*
- the name of the tarball
- and the corresponding list (manifest)

when the package first installs, it copies the name of the tarball under
/var/db/components

so that when it gets reinstalled, there's no need to extract the same files
again.

The common part to that is in bootstrap/

There are two meta packages:
- xenocara/meta, to build stuff that requires xenocara to be there
- xenocara/release, to build the remaining critical components and create 
the X release