public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: H <agents-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Installing new tarball over old?
Date: Fri, 19 May 2023 20:49:59 -0400	[thread overview]
Message-ID: <3FA2FEE1-20E9-40BA-B6C1-A39F49EE2EB1@meddatainc.com> (raw)
In-Reply-To: <4A09BC61-8F5C-4AD9-A703-3089E51EEE58-FcZObrvlYduBUy7/sJONFg@public.gmane.org>

On May 19, 2023 8:43:51 PM EDT, H <agents-FcZObrvlYduBUy7/sJONFg@public.gmane.org> wrote:
>On May 19, 2023 3:34:24 AM EDT, ThomasH <therch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>If you have the access rights, just delete the old installation. I 
>>personally prefer side-by-side installations so I can switch between
>>them 
>>(at least for some time).
>>
>>On Wednesday, May 17, 2023 at 10:52:15 PM UTC+2 H wrote:
>>
>>> On 05/17/2023 01:28 AM, ThomasH wrote:
>>>
>>> As there are so many possibilities to install some files on a
>system,
>>
>>> depending on questions like whether you want to make a system-wide
>or
>>user 
>>> installation etc., I think it is impossible to give a general
>answer.
>>If 
>>> you are the only user on the system I would leave the existing
>>system-wide 
>>> (I presume) 2.19.2 installation alone, to not mess with the CentOS
>>package 
>>> management, unpack the 3.1.2 tarball in a suitable path under my
>HOME
>>and 
>>> link to the binaries from `~/bin` which is on my PATH.
>>>
>>> On Tuesday, May 16, 2023 at 8:56:53 PM UTC+2 H wrote:
>>>
>>>> I found I have pandoc 2.19.2 installed on my CentOS 7 system,
>>installed 
>>>> as a tarball. The latest version is 3.1.2. 
>>>>
>>>> Do I need to uninstall the old version before unpacking the most
>>recent 
>>>> tarball or can I simply install over the old version and any old
>>"cruft" 
>>>> will be removed during installation? 
>>>>
>>>> -- 
>>> You received this message because you are subscribed to the Google
>>Groups 
>>> "pandoc-discuss" group.
>>> To unsubscribe from this group and stop receiving emails from it,
>>send an 
>>> email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>>> To view this discussion on the web visit 
>>>
>>https://groups.google.com/d/msgid/pandoc-discuss/0670a3f2-69f7-4a91-b6b5-145511c273ebn%40googlegroups.com
>>
>>>
>><https://groups.google.com/d/msgid/pandoc-discuss/0670a3f2-69f7-4a91-b6b5-145511c273ebn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> Well, that begs the question: how to uninstall pandoc from a system,
>
>>> regardless of whether it is installed system-wide or for an
>>individual 
>>> user? My installation of 2.19.2 was not done using yum (in which
>case
>>I 
>>> could simply have used yum to remove it) but installed as a tarball 
>>> downloaded from the pandoc github repository.
>>>
>>> If I could uninstall the current, old version, I could then install
>>the 
>>> current version. How do you update your pandoc installation on your 
>>> computer when a new release becomes available?
>>>
>
>I have the access rights but how do I find all the files that need to
>be deleted?

Oh, maybe I should just open the tarball, see which files it contains and delete them from the installation? Or is there a simpler way?

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/3FA2FEE1-20E9-40BA-B6C1-A39F49EE2EB1%40meddatainc.com.


  parent reply	other threads:[~2023-05-20  0:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 18:56 H
     [not found] ` <3ce85797-6037-9c37-1234-a583227a5f2c-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-17  5:28   ` ThomasH
     [not found]     ` <0670a3f2-69f7-4a91-b6b5-145511c273ebn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-17 20:52       ` H
     [not found]         ` <f1db6da5-7788-7288-3397-5d8f45cebfbb-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-19  7:34           ` ThomasH
     [not found]             ` <828651d0-3853-4d7a-a7c5-f0157a979737n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-20  0:43               ` H
     [not found]                 ` <4A09BC61-8F5C-4AD9-A703-3089E51EEE58-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-20  0:49                   ` H [this message]
     [not found]                     ` <3FA2FEE1-20E9-40BA-B6C1-A39F49EE2EB1-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-20  1:05                       ` John Gabriele
2023-05-20 19:31                       ` H
     [not found]                         ` <108b5469-1015-c99a-d9fb-707a37783255-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-05-20 22:58                           ` John MacFarlane
     [not found]                             ` <77D4EA6A-C0B5-41F2-B320-215958C215E8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-05-21  0:24                               ` H
2023-05-20  0:44   ` John Gabriele
  -- strict thread matches above, loose matches on Subject: below --
2023-05-16  1:39 H

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FA2FEE1-20E9-40BA-B6C1-A39F49EE2EB1@meddatainc.com \
    --to=agents-fczobrvlydubuy7/sjonfg@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).