public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Multimedia Libs
Date: Tue, 26 May 2020 19:13:38 +0200	[thread overview]
Message-ID: <43209c93-2402-b54c-7579-db3fa5030183@ipfire.org> (raw)
In-Reply-To: <27133424-2608-47D2-96C2-09B1135C8967@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 4009 bytes --]

Hi,

lets see if I can pull this together - its been a long day (holidays are
over...) - please see comments below:

On 26.05.2020 12:15, Michael Tremer wrote:
> Hi,
> 
>> On 25 May 2020, at 12:05, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>> 
>> Hi,
>> 
>> On 25.05.2020 11:29, Michael Tremer wrote:
>>> Hi,
>>> 
>>>> On 23 May 2020, at 11:08, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>> 
>>>> ...
>> 
>>>> I found a newer version of 'minidlna' in cache (1.2.1 dated 2017).
>>>> Is there a reason why we are using the older version?
>>> 
>>> Not that I am aware of. Please check the official website and send a patch with the most recent version.
>> 
>> Work in progress... ;-)
>> 
>>>> 2. Similar to 'nettle 3.6', I found a lot of dependencies (sigh). Should
>>>> I still upload the updates above, so we can take a look at them or
>>>> should I wait? I don't want to make unnecessary noise.
>>> 
>>> Dependencies to what?
>> 
>> I hope I did it right - I tried with the new 'make.sh' option:
>> 
>> ffmpeg 4.2.2:
>> ./make.sh find-dependencies libavcodec.so.58 libavdevice.so.58
>> libavfilter.so.7 libavformat.so.58 libavresample.so.4 libavutil.so.56
>> libpostproc.so.55 libswresample.so.3 libswscale.so.5
>> 
>> Output:
>> usr/sbin/minidlnad
>> usr/bin/mpd
>> usr/bin/motion
>> usr/bin/ffmpeg
>> usr/bin/ffprobe
> 
> These do not need to be shipped again, because the library’s version number did not change.

Ok, no rootfile changes + no version changes in libraries.

Besides, the same goes for 'ffmpeg 4.2.3', which I sent yesterday. No
version bumps.

>> 
>> For tcl 8.6.10:
>> ./make.sh find-dependencies libitcl4.2.0.so libtcl8.6.so
>> libsqlite3.30.1.2.so libtdbc1.1.1.so libtdbcmysql1.1.1.so
>> libtdbcodbc1.1.1.so libtdbcpostgres1.1.1.so libthread2.8.5.so
>> 
>> Output:
>> usr/bin/tclsh8.6
>> tools_i586/bin/expect
>> bin/tclsh8.6
> 
> Same here. This is actually only tcl and expect. The latter is only present in the toolchain.

Ok. Fine. Like above.

> 
>> 
>> For krb5 1.18.1:
>> ./make.sh find-dependencies db2.so otp.so pkinit.so spake.so test.so
>> k5tls.so libgssapi_krb5.so.2 libgssrpc.so.4 libk5crypto.so.3
>> libkadm5clnt_mit.so.12 libkadm5srv_mit.so.12 libkdb5.so.10 libkrad.so.0
>> libkrb5.so.3 libkrb5support.so.0 libverto.so.0
> 
> These all need to be shipped again.
> 
> I looks like it is only samba and netatalk.

Now I'm curious. "Samba and netatalk".

In fact, I do find some 'smb*'-snippets in the list below, but I
wouldn't have known what programs to look for. How did you know?

> 
>> 
>> Output:
>> sbin/key.dns_resolver
>> usr/sbin/kprop
>> usr/sbin/kdb5_util
>> usr/sbin/kpropd
>> usr/sbin/kadmin.local
>> usr/sbin/smbd
>> usr/sbin/kadmind
>> usr/sbin/sim_server
>> usr/sbin/kproplog
>> usr/sbin/winbindd
>> usr/sbin/krb5kdc
>> usr/sbin/sserver
>> usr/sbin/afpd
>> usr/sbin/nmbd
>> usr/sbin/gss-server
>> usr/sbin/uuserver
>> usr/bin/smbcquotas
>> usr/bin/kdestroy
>> usr/bin/kvno
>> usr/bin/uuclient
>> usr/bin/kinit
>> usr/bin/ntlm_auth
>> usr/bin/smbcacls
>> usr/bin/kswitch
>> usr/bin/smbspool
>> usr/bin/sclient
>> usr/bin/smbpasswd
>> usr/bin/smbget
>> usr/bin/net
>> usr/bin/gss-client
>> usr/bin/ktutil
>> usr/bin/ksu
>> usr/bin/rpcclient
>> usr/bin/kadmin
>> usr/bin/smbtree
>> usr/bin/sim_client
>> usr/bin/klist
>> usr/bin/smbclient
>> usr/bin/kpasswd
>> usr/lib/libnetapi.so.0
>> usr/lib/libkrb5.so.3.3
>> usr/lib/libwireshark.so.13.0.3
>> usr/lib/libsmbclient.so.0
>> usr/lib/libkdb5.so.8.0
>> usr/lib/libkadm5srv_mit.so.11.0
>> usr/lib/freeradius/rlm_krb5.so
>> usr/lib/libkdb5.so.10.0
>> usr/lib/libgssapi_krb5.so.2.2
>> usr/lib/libgssrpc.so.4.2
>> usr/lib/libkadm5clnt_mit.so.12.0
>> usr/lib/libkadm5clnt_mit.so.11.0
>> usr/lib/libkadm5srv_mit.so.12.0
>> usr/lib/libk5crypto.so.3.1
>> usr/lib/libkrad.so.0.0
>> 
>> Best,
>> Matthias
> 
> -Michael
> 

Best,
Matthias

  reply	other threads:[~2020-05-26 17:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5C7D0AAC-730A-40BA-B398-8AED49A4867D@ipfire.org>
2020-03-25 20:55 ` Matthias Fischer
2020-03-25 21:11   ` Stephan Mending
2020-03-26  7:24     ` Matthias Fischer
2020-03-26  9:10       ` Michael Tremer
2020-03-26  9:30         ` Matthias Fischer
2020-03-28  4:54           ` Matthias Fischer
2020-03-28  7:41             ` Michael Tremer
2020-03-26  9:47         ` Stephan Mending
2020-03-30  5:08   ` Matthias Fischer
2020-03-30  5:17     ` Matthias Fischer
2020-03-30  9:10     ` Matthias Fischer
2020-03-30  9:31       ` Michael Tremer
2020-04-02 17:07   ` Matthias Fischer
2020-04-03 10:22     ` Michael Tremer
2020-05-23 10:08   ` Matthias Fischer
2020-05-25  9:29     ` Michael Tremer
2020-05-25 11:05       ` Matthias Fischer
2020-05-26 10:15         ` Michael Tremer
2020-05-26 17:13           ` Matthias Fischer [this message]
2020-05-28 11:54             ` Michael Tremer

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=43209c93-2402-b54c-7579-db3fa5030183@ipfire.org \
    --to=matthias.fischer@ipfire.org \
    --cc=development@lists.ipfire.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