WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: onboot.lst needs check for allready existing entry  (Read 1796 times)

Offline halma

  • Full Member
  • ***
  • Posts: 164
onboot.lst needs check for allready existing entry
« on: October 13, 2015, 04:08:25 AM »
Hello,

while i play around a bit with TC and i needed to remove compiletc more then once for my playings

Code: [Select]
rm -f /mnt/xvda1/tce/optional/compiletc.tcz
rm -f /usr/local/tce.installed/compiletc

and if you reinstall compiletc.tcz with tce-load, it writes again a entry "compiletc.tcz" into onboot.lst, and the result is

cat onboot.lst
Code: [Select]
mc.tcz
openssh.tcz
bash.tcz
bash-completion.tcz
python-dev.tcz
gettext.tcz
glib2-dev.tcz
git.tcz
perl5.tcz
compiletc.tcz
squashfs-tools.tcz
glibc_apps.tcz
autoconf.tcz
pixman-dev.tcz
texinfo.tcz
compiletc.tcz
compiletc.tcz
compiletc.tcz
compiletc.tcz
compiletc.tcz
squashfs-tools.tcz

would be cool if tce-load is doing a checkup before it writes into onboot.lst that no package / extension is written double and more into onboot.lst
i know thats not the way to remove a package / extension but a checkup would be usefull anyway, ...my thinking
Thanks
Halma
1 + 2 = 6  cause  10 - 6 = 78 ;-) lol

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1702
Re: onboot.lst needs check for allready existing entry
« Reply #1 on: October 13, 2015, 04:38:54 AM »
I assume this only happens if an extension was improperly ripped out of the system, so I'd suggest to use
Code: [Select]
tce-load -wil compiletc
The  l  switch (lower case L) prevents tce-load from writing an entry to onboot.lst, but also prevents an extension that was already downloaded from being installed.
So, the following might be more reliable
Code: [Select]
tce-load -w compiletc
tce-load -i compiletc
Download a copy and keep it handy: Core book ;)

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14569
Re: onboot.lst needs check for allready existing entry
« Reply #2 on: October 13, 2015, 05:49:29 AM »
..and also:

* deleting compiletc in this manner will not delete it's deps (gcc, binutils, etc), dep or md5sum files
* ondemand was created with gui apps in mind, but hey...
* the apps gui maintenance/ondemand was created to add/remove things properly

..and it would be difficult to design tce-load to correct all possible "that's not the way to remove..." hacks  ;)