Tiny Core Linux
Tiny Core Base => TCB Bugs => Topic started by: vinnie on March 30, 2011, 12:54:28 PM
-
Today I switched to 3.6.1 and I updated several packages on the pen.
At the restart I opened appsaudit to update various packages arrears, among these vlc.
Finished updating i launch its script ondemand but it doesn't load the program.
Launched from the terminal tells me I can not find libproxy-2.7.tcz, but I had done before updating the dep file and then update the package!
I redid the operation but appsaudit not added the package
Always check with appsaudit the missing dependencies and report it to me!
Disconsolate at the end I download the package from appbrowser
Later try again because I have another pen to be updated, I hope it is just a case. ;)
-
I remade but now the new dependency still not automatically installed
Please tell us if I am wrong updating dependency files first and then the packages o se davvero c'รจ un problema.
-
Dependencies are separately handled in AppsAudit.
Check for updates checks the md5sum of applications.
Those found with a difference will be downloaded and do not take effect until after a reboot.
Upon reboot, one can and should use AppsAudit Dependencies -> Update .dep files -> Build Reporting Database -> Display All with Missing Dependencies.
Using AppsAudit Dependencies will be the only way to be sure to catch .dep files that have changed. As often the application does not change but a .dep may.
-
My process was this:
1 update. dep
2 search for the missing dependencies (libproxy reported)
3 upgrade packages
4 reboot
let me see if I understand it, you advise me to:
1 update packages
2 reboot
3 search for the missing dependencies
4 and to update them?
-
Two separate conditions:
If you hear that a .dep file has changed, you would run your first example.
When AppsAudit reports a missing dependency, then open AppBrowser and select "Download+Load" the reported on item.
Done.
When you wish to check for updates, i.e., applications with differing .md5s than yours, and you decided to update them.
Then the new applications are "loaded" upon a reboot. After such it is good policy to use AppsAudit->Build Database->Display All with Missing Dependencies.
One would expect that dependencies would not be a moving target. However as in the first example, a "new" dependency can occur without a change to the application. Therefore it is best to keep these two operations separate.
-
Well, how about a "Load Missing Dependencies" in the Dependencies tab?
-
Roberts I understand and agree with what you said but, certainly for the bad English that I use, I have not explained properly.
I thought the new missing dependencies, once established by appsaudit, were automatically installed during updating of packages and what if you could make this change might be useful, otherwise it comes off easily even with appbrowser.
One question, when I update the dependencies, is therefore also "built database?
At this point beyond that misunderstanding, I propose another idea. during the upgrade packages, when you need to select the packages you choose to update, it would be nice to see the changelog of the packages to know what's changed before you upgrade
Thanks Roberts
-
What we are talking about is not a bug, but a feature request.
-
I noted here because I thought that appsaudi also download the new dependencies and then believing in a malfunction, then I took advantagefor the features :P
-
I have made appsaudit, update extension(s) function, also check and fetch any missing (likely new) dependencies. Will be in 3.6 release candidate 2.
-
Really, thanks roberts, you're a unique developer :)