From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] sleuthkit 4.12.1
Date: Sat, 2 Mar 2024 20:12:49 +0100 [thread overview]
Message-ID: <9183006f-4fe8-4f8b-cd55-cd3b5a7f3540@t-online.de> (raw)
In-Reply-To: <d71b8f72-87cf-4296-88f0-e45594a6c547@gmail.com>
Hi Marco,
Marco Atzeri via Cygwin-apps wrote:
> On 02/03/2024 13:05, Christian Franke via Cygwin-apps wrote:
>> I would like to contribute sleuthkit. Also present in Debian, Fedora,
>> Ubuntu, ...
>>
>> SUMMARY="Tools for analysis of volume and filesystem data"
>>
>> DESCRIPTION="The Sleuth Kit (TSK) is a collection of command line tools
>> for disk images. It allows to analyze volume and filesystem data,
>> examine disk layout, recover deleted files, etc. Many partition and
>> filesystem formats are supported."
>>
>> libtsk_SUMMARY="${SUMMARY} (runtime)"
>>
>> libtsk_devel_SUMMARY="${SUMMARY} (development)"
>>
>>
>> I'm not sure about the LICENSE string:
>>
>> LICENSE="CPL-1.0 AND GPL-2.0-or-later"
>>
>> The license/README.md file mentions a bunch of licenses, see comment
>> in cygport file. CPL-1.0 is the main license, one separate tool uses
>> GPL-2.0-or-later.
>>
>>
>> The source package supports reproducible builds except for
>> libtsk-devel (timestamps in *.a files).
>
> Hi Christian,
>
> usually we do no distribute static library
Didn't know, sorry. Makes plenty of sense, at least to prevent that
other packages accidentally link to the static lib.
>
> Any reason here ?
No, static lib removed.
> except that GTG
>
> $ git diff |grep "^+"
> +++ b/cygwin-pkg-maint
> +sleuthkit Christian Franke
>
Thanks,
Christian
prev parent reply other threads:[~2024-03-02 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 12:05 Christian Franke
2024-03-02 16:43 ` Marco Atzeri
2024-03-02 19:12 ` Christian Franke [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=9183006f-4fe8-4f8b-cd55-cd3b5a7f3540@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin-apps@cygwin.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).