Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 Sep 2014 08:00:11 +0200
From:      Marcus von Appen <mva@FreeBSD.org>
To:        freebsd-ports@freebsd.org
Subject:   Re: [BRAINSTORMING] simplifying maintainer's life
Message-ID:  <20140904060011.GB1044@medusa.sysfault.org>
In-Reply-To: <20140903212243.GK63931@graf.pompo.net>
References:  <20140903082538.GE63085@ivaldir.etoilebsd.net> <20140903145614.158f8e89@kalimero.tijl.coosemans.org> <20140903135029.GK63085@ivaldir.etoilebsd.net> <20140903165622.3bff54e0@kalimero.tijl.coosemans.org> <20140903150018.GL63085@ivaldir.etoilebsd.net> <5407649A.80500@FreeBSD.org> <20140903191256.GB1025@medusa.sysfault.org> <20140903212243.GK63931@graf.pompo.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--Y7xTucakfITjPcLV
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On, Wed Sep 03, 2014, Thierry Thomas wrote:

> Le mer  3 sep 14 =C3=A0 21:12:56 +0200, Marcus von Appen <mva@FreeBSD.org>
>  =C3=A9crivait=C2=A0:
>
> > On, Wed Sep 03, 2014, Bryan Drewery wrote:
>
> > [...]
> >
> > > I understand there is fear involved with not having a plist validate
> > > everything. Consider that many other package systems do not require a
> > > plist to start.
> >
> > [...]
> >
> > Seconded. In my opinion for 95% of all cases it sums up to: everything =
in the
> > staging directory gets installed. We can use post-build or pre-install =
to
> > clean up the staging directory where necessary, or even revert the plist
> > meaning in the worst case, e.g. everything in ${EXCLUDE_INSTALL} is not=
 to be
> > installed, if necessary.
>
> I disagree. I use plist for two things:

You belong to the +-5% ;-).


> - when upgrading a port, I compare the previous plist with the newer
>   one, and if some important files are missing, I try to understand the
>   reason;

For those things a comparision mechanism in the qa scripts for a
porter/committer might come in handy:

- get stagedir contents
- get (current) package contents
- compare and show a list of changes for the QA

> - I often grep all plists to find which port could possibly provide such
>   header or such library (among non-installed ports, of course).

I do the same, but would argue that such a query service should belong to or
offered by a pkg search (as sort of counterpart to pkg which).

Cheers
Marcus

--Y7xTucakfITjPcLV
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlQH/+sACgkQi68/ErJnpkfX5QCgtbAnZgMAB66kjVcVsqABC8Li
wqEAnAgQ63rhJp8qHyVzphAlUhL7/uXA
=qPeg
-----END PGP SIGNATURE-----

--Y7xTucakfITjPcLV--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140904060011.GB1044>