Results 1 to 7 of 7

Thread: Coding editors

  1. #1
    Join Date
    Dec 2008
    Location
    Montana, USA
    Posts
    676

    Default Coding editors

    I'd like to try using Komodo Edit but it is not provided in the packman repository. I can't find a .rpm package. I have the tar.gz file but don't see an uninstall script in the package. How can I be sure I can cleanly uninstall this program if I decide I don't want to use it?

    The same question applies to eclipse.

    Bart

  2. #2
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,324
    Blog Entries
    15

    Default Re: Coding editors

    Quote Originally Posted by montana_suse_user View Post
    I'd like to try using Komodo Edit but it is not provided in the packman repository. I can't find a .rpm package. I have the tar.gz file but don't see an uninstall script in the package. How can I be sure I can cleanly uninstall this program if I decide I don't want to use it?

    The same question applies to eclipse.

    Bart
    Hi
    I normally extract the tarball (including eclipse) and just run manually from a /data/applications directory and create a desktop entry in ~/.local/spare/applications to the binary.. in the case of komodo edit to run for me it's just;
    Code:
    /data/applications/Komodo-Edit-11.0.2-18122-linux-x86_64/INSTALLDIR/bin/komodo
    It stores it's user file in ~/.komodoedit this could also be moved and a softlink created.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  3. #3
    Join Date
    Dec 2008
    Location
    Montana, USA
    Posts
    676

    Default Re: Coding editors

    Looking at the tar file, there's about a million lib* files and other things that I *assume* would be installed in among the already existing files. I'm concerned that if I remove komodo, there would be a ton of "stuff" left on my drive. As I understand, that was the whole idea behind rpm. Would installing as you describe result in all the files being installed in /data/applications/komodo directory so a deletion of that directory and the ~/.komodoedit directory would remove the whole mess?

    Bart

  4. #4
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,324
    Blog Entries
    15

    Default Re: Coding editors

    Quote Originally Posted by montana_suse_user View Post
    Looking at the tar file, there's about a million lib* files and other things that I *assume* would be installed in among the already existing files. I'm concerned that if I remove komodo, there would be a ton of "stuff" left on my drive. As I understand, that was the whole idea behind rpm. Would installing as you describe result in all the files being installed in /data/applications/komodo directory so a deletion of that directory and the ~/.komodoedit directory would remove the whole mess?

    Bart
    Hi
    You are correct, just removing the directory(s) will result in it's removal, oh and possibly the desktop file in ~/.local/share/applications. That's why I do it that way, also I can isolate over an upgrade/re-install by using symlinks and then script out a home_configuration to add them all back if required...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  5. #5
    Join Date
    Dec 2008
    Location
    Montana, USA
    Posts
    676

    Default Re: Coding editors

    Ahah! That's going to work quite well for me! I'll print this thread and add it to my Cook book. Thanks a lot!

    Bart

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    32,324
    Blog Entries
    15

    Default Re: Coding editors

    Quote Originally Posted by montana_suse_user View Post
    Ahah! That's going to work quite well for me! I'll print this thread and add it to my Cook book. Thanks a lot!

    Bart
    Hi
    So I renamed things...
    I called the top directory (under applications)
    Komodo
    Under here renamed the INSTALLDIR to komodo_app and moved ~/.komodoedit to komodo_home

    Code:
    mv ~/.komodoedit /data/applications/Komodo/komodo_homedir
    ln -s /data/applications/Komodo/komodo_homedir ~/.komodoedit
    cp /data/applications/Komodo/komodo_app/share/icons/komodo48.png ~/.icons/komodo.png
    
    vi ~/.local/share/applications/komodo.desktop
    
    [Desktop Entry]
    Name=Komodo Edit
    Comment=Polyglot editor
    Exec=/data/applications/Komodo/komodo_app/bin/komodo %F
    Terminal=false
    Type=Application
    Icon=komodo
    Categories=Utility;TextEditor;
    If you wanted to script out the desktop file creation in a script it would be;
    Code:
    cat > ~/.local/share/applications/komodo.desktop <<EOF
    [Desktop Entry]
    Name=Komodo Edit
    Comment=Polyglot editor
    Exec=/data/applications/Komodo/komodo_app/bin/komodo %F
    Terminal=false
    Type=Application
    Icon=komodo
    Categories=Utility;TextEditor;
    EOF
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: Coding editors

    Depending on the IDE,
    Plenty can happen to your Development machine, not just the initial installation but also later installation of libraries to support your project... Which, depending on your setup and configuration might be installed in your system directories and not necessarily in your IDE directory tree.

    This a major reason why I heavily use virtualization for every one of my coding projects, to isolate and ensure no cross-contamination between each build environment.

    Virtualization grants you additional benefits as well...
    Better system stability
    Easy backups
    Easy to revert or make copies and snapshots at specific points

    HTH,
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •