How do conditionalize plist on $NOPORTDOCS

[Wesley Shields]

On Tue, Nov 18, 2008 at 01:38:52PM -0500, Martin Cracauer wrote:
> Wesley Shields wrote on Tue, Nov 18, 2008 at 01:36:23PM -0500: 
> > On Tue, Nov 18, 2008 at 01:30:33PM -0500, Martin Cracauer wrote:
> > > > >>> While we are talking, how do you guys thing I should handle this
> > > > >>> problem: it's a binary port.  There are different binaries for
> > > > >>> FreeBSD-6.x, 7.x, 8.x
> > > > >>> http://common-lisp.net/project/cmucl/downloads/release/19e/
> > > > >>>
> > > > >>> The 6.3 will run everywhere.  Should I just use that one? Do you want
> > > > >>> me to conditionalize on FreeBSD version?
> > > > >> If they bother to release different native binaries for our supported
> > > > >> OS versions let encourage them to keep doing that ;-)
> > > > > 
> > > > > "They" == kind of me, although I didn't build these particular
> > > > > binaries.
> > > > > 
> > > > > Is there prior art in ports about how to do this? What do I do with
> > > > > oddball version numbers?
> > > > 
> > > > Perhaps you can conditionalize the DISTNAME based on the FreeBSD version
> > > > number, as shown on this page:
> > > > http://www.freebsd.org/doc/en/books/porters-handbook/freebsd-versions.html?
> > > > 
> > > > If you do that, just make sure that the distinfo file has an entry for
> > > > each possible DISTNAME value, so the checksum verification will work on
> > > > any FreeBSD version.
> > > 
> > > So what happens when a user runs FreeBSD-6, installs such a port,
> > > then upgrades to FreeBSD-7.
> > > 
> > > Would the port for the installed package come up with the wrong plist
> > > and whatnot?
> > 
> > Maybe I'm misunderstanding what you're asking but if the port installs
> > different files based upon the version it's being installed on it should
> > use PLIST_SUB accordingly.
> > 
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/plist.html
> 
> But you'd have the wrong one installed.  Your freebsd-7 would have the
> freebsd-6 package installed and the installed files don't match.

Yes, but the plist would still be correct.  The installed files would
match the plist.  You would want to update the port though so that you
get the updated files, which would cause the plist to be registered
again ensuring that things remain consistently correct.

> On second thought, I don't think it matters since it's not different
> from having /usr/ports/lang/cmucl/* updated to something new.  Never mind.

Yes, I don't see this as a problem at all.

-- WXS