Port has different versions for different architectures...

Pav Lucistnik pav at FreeBSD.org
Tue Jun 1 11:01:39 PDT 2004

V út, 01. 06. 2004 v 17:09, Tim Bishop píše:

> Say a new version of a package has been released for one arcitecture,
> but not others, how can this be dealt with in a port?
> I'd want to do something _like_ this (but not this):
> .if ${ARCH} == "i386"
> .else
> .endif
> I'm sure there are numerous bodges to doing this in the port, but I
> suspect this will break things such as the INDEX file.

No, it will not break INDEX file. It will just result in different INDEX
file for each architecture.

> A solution would be to maintain multiple versions of the same port, but
> that seems like overkill. Unless slave ports are used?

If plist don't change between versions, I don't see much problems with
your approach. Otherwise you can wait with the update until all archs
are available, or temporarily comment out laging architectures.

Pav Lucistnik <pav at oook.cz>
              <pav at FreeBSD.org>

 I went grocery shopping, made a pot of chilli, played ey,
then ate some chilli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: Toto je =?iso-8859-2?Q?digit=E1ln=EC?=
	=?ISO-8859-1?Q?_podepsan=E1?= =?iso-8859-2?Q?_=E8=E1st?=
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040601/fa6863a8/attachment-0001.bin

More information about the freebsd-ports mailing list