×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Atikccd 1.29

  • Posts: 95
  • Thank you received: 14

Replied by Phil Shepherd on topic Atikccd 1.29

Yep - I had the same issue... copying the xml file, as per your post, to where the rest were sorted the issue...

Did you notify CloudMakers of the issue? Peter is a regular poster on here... If not, I shall...

Phil
Last edit: 5 years 5 months ago by Phil Shepherd.
5 years 5 months ago #30627

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Atikccd 1.29

Well, this is actually more a philosophical question than a bug :)

By definition /usr is for software, which can be overwritten by system update and as far as Atik driver (unlike the rest of INDI) is not distributed over such channel, the correct place is /usr/local. To be honest, I'm not sure if it this location is used by all our binary packages, the target location is not hardcoded in cmake configuration, but it defaults to /usr/local. Maybe I changed it manually before and forgot to do it in recent builds. That's why the result may be inconsistent. But actually, whatever location we'll choose, one half of users will complain, am I right? :)

My opinion is, that if INDI driver can be installed in both /usr and /usr/local subtrees, the any INDI software should check both.

The simple workaround is to make symbolic link from /usr/local/share/indi/indi_atik.xml to /usr/share/indi.

Regards, Peter
5 years 5 months ago #30639

Please Log in or Create an account to join the conversation.

  • Posts: 95
  • Thank you received: 14

Replied by Phil Shepherd on topic Atikccd 1.29

LOL - yep... 1/2 will complain....

TBH, Peter... I agree with you that any non-system stuff ought to go into /usr/local - I have made the argument at work too & most people tend to agree there....

Indeed I have since created a symbolic link as hindsight made me change it...

I suppose Jasem could make a call as to which should be the standard place?

Phil
5 years 5 months ago #30641

Please Log in or Create an account to join the conversation.

  • Posts: 472
  • Thank you received: 165

Replied by Jarno Paananen on topic Atikccd 1.29

The package is a bit inconsistent as it places everything else in /usr except that one xml file:
~$ dpkg -L atikccd
/lib
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/99-atik.rules
/usr
/usr/bin
/usr/bin/atik_ccd_test
/usr/bin/indi_atik_ccd
/usr/bin/indi_atik_wheel
/usr/lib
/usr/lib/libatikccd.a
/usr/lib/libatikccd.so.1.29
/usr/local
/usr/local/share
/usr/local/share/indi
/usr/local/share/indi/indi_atik.xml
/usr/lib/libatikccd.so
/usr/lib/libatikccd.so.1
5 years 5 months ago #30647

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Atikccd 1.29

Since version 1.30 everything is placed into /usr/local so pls. make sure to remove old executables.

/usr/bin/atik_ccd_test
/usr/bin/indi_atik_ccd
/usr/bin/indi_atik_wheel

Peter
The following user(s) said Thank You: Thomas Seckler, Gebhard
5 years 5 months ago #30933

Please Log in or Create an account to join the conversation.

  • Posts: 30
  • Thank you received: 0

Replied by Gebhard on topic Atikccd 1.29

I think one should remove older atikccd completely prior to install 1.30
sudo apt purge atikccd

to remove the remaining libs in /usr/lib and indi_atik_xml in /usr/share/indi/.
Strange this move to local but
Your desire is your heaven.

Cherno
5 years 4 months ago #31165

Please Log in or Create an account to join the conversation.

  • Posts: 30
  • Thank you received: 0

Replied by Gebhard on topic Atikccd 1.29

1.30 was found but I was not able to set frame start and frame height via
indi_setprop "Atik 460ex CCD.CCD_FRAME.X=200"
indi_setprop "Atik 460ex CCD.CCD_FRAME.HEIGHT=500"

Switching back to 1.26

cherno
5 years 4 months ago #31166

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Atikccd 1.29

Yes, it is better to remove previous package first. And until Jasem will fix the bug in Ekos (it searches just /usr/bin for drivers) also to make symlinks from /usr/local to /usr for bin/indi_atik_ccd, bin/indi_atik_wheel and share/indi_atik.xml. Peter
5 years 4 months ago #31170

Please Log in or Create an account to join the conversation.

  • Posts: 210
  • Thank you received: 104

Replied by Patrick Chevalley on topic Atikccd 1.29

Hi Peter,

I think you misinterpreted the use of /usr/local , at least in Debian.
From wiki.debian.org/FilesystemHierarchyStandard :
/usr/local/bin : locally compiled binaries, local shell script, etc.
So when you compile the atik driver in your computer you must install in /usr/local, but when you distribute .deb packages this must go to /usr because in this case you are the system distributor for this software, it will never been found in Debian system packages.

Sure there is other interpretation, FreeBSD is an extreme case but here we speak about deb packages.

But you are free to make your packages as you intend.

Here as small script for user like me that prefer /usr:
#!/bin/bash
for pkg in $(ls atikccd-*.deb); do
  dpkg-deb -R $pkg tmp
  if [[ $? != 0 ]]; then echo error ; exit; fi
  rm tmp/DEBIAN/md5sums
  mv tmp/usr/local/* tmp/usr/
  rmdir tmp/usr/local
  fakeroot dpkg-deb -Zxz --build tmp .
  rm -rf tmp
done

Patrick
The following user(s) said Thank You: Jasem Mutlaq, Thomas Seckler
5 years 4 months ago #31189

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Atikccd 1.29

Hi Patrick, as I wrote already in this thread, whatever place I'll choose, half of the users will complain, it makes no sense to argue :)

/usr/bin is for distribution-managed normal user programs.
/usr/local/bin is for normal user programs not managed by the distribution package manager, e.g. locally compiled packages. You should not install them into /usr/bin because future distribution upgrades may modify or delete them without warning.


I don't think that driver downloaded manually from our web is managed by the distribution package manager. On some operating systems (and maybe also on some Linux distros) it is not possible at all to write something to /usr/bin.

INDI driver is an executable. It can be located wherever executable can be located. It works also with indiserver this way and there is no reason why it shouldn't work with Ekos. If it doesn't work, it should be fixed.

Peter
5 years 4 months ago #31191

Please Log in or Create an account to join the conversation.

Replied by Jasem Mutlaq on topic Atikccd 1.29

All Linux INDI drivers are installed to /usr/bin, so atikccd should not an exception to this IMO.
5 years 4 months ago #31195

Please Log in or Create an account to join the conversation.

  • Posts: 712
  • Thank you received: 174

Replied by Peter Polakovic on topic Atikccd 1.29

Jasem, sorry, but you're apparently wrong, as you can see, e.g. Atik driver is installed to /usr/local/bin :)
5 years 4 months ago #31198

Please Log in or Create an account to join the conversation.

Time to create page: 0.835 seconds