exclude.list.template

[wfrcrd]

Hi ( sorry for my bad english, and for my very poor knowledge) thank you for the project!
I've used systemback since long time to clone systems and now I'm trying eggs on mint victoria.
I've noticed that on a cloned system some programs din't work properly, something from the original system was missing.
After 2 days of trying I've noticed that inside the exclude.list.template there was some libraries , which was not trasferred to the new system ( I'm away from the pc at the moment , so I cannot tell exactly, but it was something referred to : lib32gcc-s1 and or libc6:i386 ).

So I remove those lines from the exclude.list.template file, restart the produce activity and on the live the programs seems to work, ( I've problems to install the system from the live but that's another story I suppose).

My question is : WHO wrote those lines on the exclude.list.template file without any advice, and WHY ? :-)

Thank you for you great job!

[pieroproietti]

Hi @wfrcrd

It happen! We toke part of the exclusions from bleachbit... so probably the reason is that.

But with feedback we can allways adapt or rollback.

I went now to search for lib32gcc-s1 and saw from this link it is installed under: /usr/lib32/ and /usr/share/doc/, so they are not excluded.

The same seem for libc6:i386 this are the installed files, I'm just checking now but I don't found any paths deleted from the actually exclude.list.

If you can tell exacly the line responsable for your problem I can update the exclude.list.template.

Don't worry for your english, is enought to express and comunicate, mine is not so good too.

Thanks for feedback, it's important

[wfrcrd]

These are the lines I've deleted from the exclude.list.template file :

usr/bin/x86_64-w64-mingw32-cpp-win32 usr/bin/x86_64-w64-mingw32-gcc-12-win32 usr/bin/x86_64-w64-mingw32-gcc-ar-win32 usr/bin/x86_64-w64-mingw32-gcc-nm-win32 usr/bin/x86_64-w64-mingw32-gcc-ranlib-win32 usr/bin/x86_64-w64-mingw32-gcc-win32 usr/bin/x86_64-w64-mingw32-gcov-dump-win32 usr/bin/x86_64-w64-mingw32-gcov-tool-win32 usr/bin/x86_64-w64-mingw32-gcov-win32 usr/bin/x86_64-w64-mingw32-lto-dump-win32 usr/i686-w64-mingw32/* usr/include/gtkmm-3.0/* usr/lib/gcc/i686-w64-mingw32/* usr/lib/gcc/x86_64-w64-mingw32/* usr/lib/i386-linux-gnu/* usr/lib/i386-linux-gnu/libLLVM-12.so usr/lib/i386-linux-gnu/libLLVM-12.so.1 usr/lib/llvm-11/* usr/lib/llvm-9/* usr/lib/mono/* usr/lib/snapd/* usr/lib/x86_64-linux-gnu/libLLVM-10.so usr/lib/x86_64-linux-gnu/libLLVM-10.so.1 usr/lib/x86_64-linux-gnu/libLLVM-11.so usr/lib/x86_64-linux-gnu/libLLVM-11.so.1 usr/lib/x86_64-linux-gnu/libLLVM-12.so usr/lib/x86_64-linux-gnu/libLLVM-12.so.1 usr/lib/x86_64-linux-gnu/libLLVM-14.so usr/lib/x86_64-linux-gnu/libLLVM-14.so.1 usr/lib/x86_64-linux-gnu/libLLVM-9.so usr/lib/x86_64-linux-gnu/libLLVM-9.so.1 usr/lib/x86_64-linux-gnu/openblas-pthread/* usr/share/dict/* usr/share/doc/* usr/share/eclipse/* usr/share/gimp/2.0/help/en/images/* usr/share/gtk-doc/html/* usr/share/krita/* usr/share/texmf/* usr/share/xemacs21/* usr/x86_64-w64-mingw32/*

[pieroproietti]

OK, I checked on the template, and understood who probably is better to not touch nothing under /usr, so I just added another filter for usr with the exclusions you delete, and you can decide if use it or not, depending on your system.

It is at last a fast solution, really it's too much materials to can decide for all, so is better the user take the responsability to fileter or not /usr.

Thanks @wfrcrd

[wfrcrd]

Thanks to you Piero !
One question : where may I find the documentation about the use of the filters you mentioned?
I'd like to exlcude an entire partition of the disk, it is possibile?

[pieroproietti]

Of course you can, you can write yours exclusion in /etc/penguins-eggs.d/exclude.list.d/exclude.list.custom and use: sudo eggs produce --filters custom .

To have a sample, i have a /private path in my root, add:

private/*

exclude all inside home/personal

home/personal/*

and so on.

[wfrcrd]

Sorry but I still miss something ...
1 if we don't use any "filter" specification , the "exclude.list.template" file will be applied ( wich is a bit strange to me, anyway..)
2 if we use the "custom" specification as ( sudo eggs produce --filters custom) what filters are applied ? exclude.list.template AND custom? or ONLY the custom? and what about the "home" file?

Sorry Piero , but I can't find any documentation about it, thank you !!

[pieroproietti]

Hi @wfrcrd

The things we clean on template are OK, must to be applied! Why clone the cache, hardware dependant files and so on?

If you use sudo eggs produce --filters custom will applied just that is in exclude.list.template and on exclude.list.custom, but actually you can edit exclude.list.template as well, it's just a text file and replace it.

I basically called it template, because inside, in creating the actual exlude.list the variables at the bottom, {{{ homes_exclude}}}, etc are replaced by the contents of the respective files.

That is, you could also, if you find the template exclusions limiting, rewrite it to your liking and use your own.

The exlude.list.homes is different, if you say it, you can see every lines start with:
home/*/something

So in this case we filter /home/piero/something but also /home/artisan/something and so on.

We choose reasonable exclusions here, but - of course - for one can be ok remove /home/piero/.wine for a gamer not!

It's an important - but too large - argument to accomplish all the cases. We are trying to find a way...

[wfrcrd]

Thanks a lot for clarify me and for your patience too!