Matthias Apitz wrote:
While I don't think there will be differences I won't know until I do
it. Call it reassurance.
El día Saturday, November 14, 2009 a las 07:51:17AM -0800, Chris escribió:
I have a somewhat flaky system. I would like to compile ports to
packages multiple times and do a file comparison. ...
What is behind the idea to compile and pack a given port twice if there
are no errors during the build?
To me it seems like a good stress test.
Also every time I update my ports tree I don't know what is going to
break. I have a
jail running all the time to recompile my ports as they are updated. I
three to five different different ports/packages branches of different
The system is somewhat flaky and crashes sometimes. I play with a lot
and am actually using Freebsd as my desktop. I am sure that most of my
due to multiple jails and using nullfs and unionfs but that isn't
relevent to my current post.
I'm also thinking of building a simple checksum database to track what
and what my options were when I compiled it. It would allow me to
regression decisions. I could also be free to delete packages and know
if I recompile
it later that it was the exact same package with the exact same
options. Very simple
script to do that. Also if say there was an option when compiling ports
to produce files
with specific time/dates it would be helpful in pinpointing which of my
a specific file came from.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"