----- Original Message -----
From: Jiri Pirko <jpirko(a)redhat.com>
To: Radek Pazdera <rpazdera(a)redhat.com>
Cc: lnst-developers(a)lists.fedorahosted.org
Sent: Fri, 02 Nov 2012 18:56:51 -0400 (EDT)
Subject: Re: LNST tools packages
Fri, Nov 02, 2012 at 08:59:03PM CET, rpazdera(a)redhat.com wrote:
Hi!
I was working on the patches with the test modules/tools transferring and caching while it
occurred to me that the tool .tar.gz packages that we plan to do are not such a good
idea.
The current implementation requires the tools to be packaged in an archive. But that is
far from convenient when it comes to developing new tests. The users would have to
recreate the archive each time they change something. That would be really tedious thing
to do. On top of that there would certainly be some problems with including those archives
in Fedora packages.
LNST could do this automatically with ease. Creating the archive is straight-forward, the
only problem is keeping track of the hashes. It would be really inefficient to
recreate all the archives each time nettestctl is executed just to compute their hashes.
I'm not really sure how to do it yet. Maybe check modify times of all the files? Or we
could invent some clever way of computing hashes of directories! That could work ... We
could cache the dir hashes in lets say ~/.lnst/.resources or something or maybe it
won't be necessary to cache them at all ...
What is your opinion this?
How about to expect packages as directories and tar'em on fly.
Same
files~same tar~same hash.....
That could work as well, but LNST would have to tar all the tools to compute the hashes on
every execution of nettestctl. That could get pretty slow with many tools directories ...
Jiri
Cheers
Radek
_______________________________________________
LNST-developers mailing list
LNST-developers(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/lnst-developers