Date: Mon, 6 Oct 2008 14:28:48 +0400 From: Eygene Ryabinkin <rea-fbsd@codelabs.ru> To: Mel <fbsd.hackers@rachie.is-a-geek.net> Cc: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org, Miroslav Lachman <000.fbsd@quip.cz>, bug-followup@freebsd.org Subject: Re: ports/126853: ports-mgmt/portaudit: speed up audit of installed packages Message-ID: <fBeVL1niDy9KJaVLxcjTW9Xe1Wo@De93eau6bBqwYjK6U3wF/jjVMVE> In-Reply-To: <200810061124.55209.fbsd.hackers@rachie.is-a-geek.net> References: <WGReTVL6CLts/44OKi4qLEsAGHs@jm/Q2DKg1djxmpGNf45V%2BWpjPIE> <48E94281.8010300@quip.cz> <fBWJkCKjscsePzEEmCUQJBXc15o@Vw/vnYB8jgSxjLDGajBSHdBTgp4> <200810061124.55209.fbsd.hackers@rachie.is-a-geek.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--0a51aUHJSNYMigeV
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Mel, good day.
Mon, Oct 06, 2008 at 11:24:54AM +0200, Mel wrote:
> On Monday 06 October 2008 07:23:37 Eygene Ryabinkin wrote:
> > But downloading the INDEX file from the central server seemed to be the
> > best way, since it almost always gives one the latest port versions, so
> > I had implemented this in a first place.
>=20
> I've been following this, but I don't agree that (port|pkg_)audit should =
do=20
> this, from the very perspective you're writing this program from:
The download is done not by the portaudit itself, but by the helper
script, portaudit-checknew.
> On Sunday 28 September 2008 11:49:18 Eygene Ryabinkin wrote:
> > 4. I feel that it is Unix-way to do the things: create small utilities
> > that do their (small) job in a proper fashion.
>=20
> Instead, it can provide installed-pkgname<seperator>pkgorigin output. The=
n,=20
> any utility can check whether a new version is available, using what ever=
=20
> source it finds relevant.
>
> For example, it is completely irrelevant if a new version is available on=
the=20
> FreeBSD servers, when your machine uses a buildserver in a local network.=
For=20
> those machines it's relevant whether their build server has a new version=
and=20
> one can automatically upgrade if one so desires.
> Similarly, if your /usr/ports is ahead of the FreeBSD's INDEX.bz2, you're=
=20
> again reporting false information.
I hear you, but it seems to me that I should just equip
portaudit-checknew with the other sources of a new ports information and
provide tunables for their location (on-disk path, URL, etc). I am
planning to do this, but first I want to know if these patches will be
viable for the project: feeding these into the /dev/null or just using
them locally, but equipping with a lot of functionality, is not what I
really want ;))
> It's also quite trivial to provide this availibility information in a dai=
ly=20
> security script, for the "majority of cases"
Didn't get it, sorry. Could you, please, elaborate a bit?
> and it's better to have tunables=20
> like _use_remote_portindex, _use_portsdir=3D/bigdisk/usr/ports in a scrip=
t.
Yes, it was what I had talked about above in this mail.
Thanks for the input!
--=20
Eygene
_ ___ _.--. #
\`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard
/ ' ` , __.--' # to read the on-line manual =20
)/' _/ \ `-_, / # while single-stepping the kernel.
`-'" `"\_ ,_.-;_.-\_ ', fsc/as #
_.-'_./ {_.' ; / # -- FreeBSD Developers handbook=20
{_.-``-' {_/ #
--0a51aUHJSNYMigeV
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
iEYEARECAAYFAkjp6GAACgkQthUKNsbL7YhIiwCfaxk/raGBCgtCRoPUirA9AM1F
QWQAoKHacwvF3w+HOUw1kMJwFJUg3hrq
=ee1X
-----END PGP SIGNATURE-----
--0a51aUHJSNYMigeV--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fBeVL1niDy9KJaVLxcjTW9Xe1Wo>