public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: blinux-list@redhat.com
Subject: Re: Alien::SVN
Date: Thu, 2 Apr 2020 00:20:21 +0200	[thread overview]
Message-ID: <e5a68357-715e-73d6-e102-49ba413e5c6c@slint.fr> (raw)
In-Reply-To: <2cbaa949-3333-4bdb-c2a0-1b1880f66051@slint.fr>

Sorry I missed one command (and included an useless one):

lftp -c "mirror  http://slackware.uk/slackware/slackware64-current/source/d/subversion/"
cd subversion
su # you need to be root to build the package
sh subversion.SlackBuild

Le 02/04/2020 à 00:16, Didier Spaier a écrit :
> Hi,
> 
> I am Didier Spaier, Slint maintainer.
> 
> At time of writing we ship this pacakage coming from Slackware64-14.2:
> http://slackware.uk/slackware/slackware64-14.2/patches/packages/subversion-1.9.7-x86_64-1_slack14.2.txz
> 
> The package you mentioned is for Slackware64-current intended to prepare
> the release of Slackware-15.0.
> 
> So:
> 1. If there is no real need to upgrade, keep the package shipped in Slint.
> 1. If you have a real need to upgrade (which one?), better use the source files
> and build a Slackware package. Generally speaking you can do it this way:
> 
> lftp -c "mirror  http://slackware.uk/slackware/slackware64-current/source/d/subversion/"
> CWD=$(pwd)
> cd subversion
> su # you need to be root to build the package
> 
> But in this case the build fails with this error:
> configure: error: cannot find kf5-config
> 
> Probably this version needs something not shipped in Slackware64-14.2, I didn't investigate further.
> 
> Best regards,
> 
> Didier
> 
> 
> Le 01/04/2020 à 18:30, Linux for blind general discussion a écrit :
>> Hi!
>>
>> On Wed, 1 Apr 2020 11:59:37 -0400
>> Linux for blind general discussion <blinux-list@redhat.com> wrote:
>>
>>> Distribution slint. SVN::Core came up as unparseable in cpanp with use of
>>> o command to check for out of date modules. I'm using cpanp to install
>>> this and the package claims to still be building and by 2:00PM today it
>>> will have taken 24 hours to build. I could just trash the build as I've
>>> done before but am curious as to possible beneficial effects of having
>>> SVN::Core unparseable go away and have that updated. On Wed, 1 Apr 2020,
>>> Linux for blind general discussion wrote:
>>>
>>
>> Since slint is based on slackware then according to
>> https://slackware.pkgs.org/current/slackware-x86_64/subversion-1.13.0-x86_64-3.txz.html
>> - subversion there (and SVN/Core.pm ) is at the latest version. No need to
>> upgrade and I suggest you kill the build.
>>
>>>> Date: Wed, 1 Apr 2020 02:04:27
>>>> From: Linux for blind general discussion <blinux-list@redhat.com>
>>>> To: Linux for blind general discussion <blinux-list@redhat.com>
>>>> Subject: Re: Alien::SVN
>>>>
>>>> Hi!
>>>>
>>>> On Tue, 31 Mar 2020 19:38:21 -0400
>>>> Linux for blind general discussion <blinux-list@redhat.com> wrote:
>>>>  
>>>>> is Alien::SVN supposed to take several hours to install?
>>>>> If no, that's what's happening over here.
>>>>> If I ever run this again I think I want to watch perl code execution as it
>>>>> happens when this one installs.
>>>>>  
>>>>
>>>> Did you manage to sort it out by now? If not, can you provide more details
>>>> about:
>>>>
>>>> 1. your distro+version
>>>>
>>>> 2. why do you need Alien::SVN?
>>>>
>>>> 3. How are you installing it?
>>>>
>>>> See https://github.com/shlomif/writing-the-perfect-question .
>>>>
>>>> Thanks!
>>>>
>>>>  
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Blinux-list mailing list
>>>>> Blinux-list@redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/blinux-list
>>>>>  
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Shlomi Fish       https://www.shlomifish.org/
>>>> https://www.shlomifish.org/humour/ways_to_do_it.html
>>>>
>>>> Chuck Norris will kill you just for the fun of kicking your Death's ass
>>>> till it runs away, then beating your soul back into your corpse. (by
>>>> e-neko). ? http://www.shlomifish.org/humour/bits/facts/Chuck-Norris/
>>>>
>>>> Please reply to list if it's a mailing list post - http://shlom.in/reply .
>>>>
>>>>
>>>> _______________________________________________
>>>> Blinux-list mailing list
>>>> Blinux-list@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/blinux-list  
>>>
>>
>>
>>


      reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Alien::SVN Linux for blind general discussion
 ` Alien::SVN Linux for blind general discussion
   ` Alien::SVN Linux for blind general discussion
     ` Alien::SVN Linux for blind general discussion
       ` Alien::SVN Linux for blind general discussion
         ` Linux for blind general discussion [this message]

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=e5a68357-715e-73d6-e102-49ba413e5c6c@slint.fr \
    --to=blinux-list@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).