From: Christian Franke <Christian.Franke@t-online.de>
To: Jon Turney <jon.turney@dronecode.org.uk>, cygwin-apps@cygwin.com
Subject: Re: [PATCH setup 2/2] Detect filename collisions between packages
Date: Mon, 24 Apr 2023 18:26:15 +0200 [thread overview]
Message-ID: <d9404b60-a482-2b65-ec69-ec13a178b459@t-online.de> (raw)
In-Reply-To: <20230423144330.3107-3-jon.turney@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2883 bytes --]
Jon Turney via Cygwin-apps wrote:
> Detect filename collisions between packages
> Don't check filenames under /etc/postinstall/ for collisions
> Report when filename collisions exist
> Add option '--collisions' to enable
IMO a useful enhancement.
> Notes:
>
> Reading file catalog from a package is moderately expensive in terms of
> I/O: To extract all the filenames from a tar archive, we need to seek to
> every file header, and to seek forward through a compressed file, we
> must examine every intervening byte to decompress it.
>
> This adds a fourth(!) pass through each archive (one to checksum it, one
> to extract files, another one (I added in dbfd1a64 without thinking too
> deeply about it) to extract symlinks), and now one to check for filename
> collisions).
>
> Using std::set_intersection() on values from std::map() here is probably
> a mistake. It's simple to write, but the performance is not good.
A faster alternative which avoids set_intersection calls in a loop is
possibly to use one large data structure which maps filenames to sets of
packages. Using multimap<string, string> instead of the straightforward
map<string, set<string>> needs possibly less memory (not tested). But
for multimap it is required that file/package name pairs are not
inserted twice.
I attached a small standalone POC source file using multimap. It would
also detect collisions in the already installed packages.
> ...
> diff --git a/filemanifest.h b/filemanifest.h
> new file mode 100644
> index 0000000..cc6fb81
> --- /dev/null
> +++ b/filemanifest.h
> @@ -0,0 +1,29 @@
> +/*
> + * Copyright (c) 2022 Jon Turney
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> + *
> + * A copy of the GNU General Public License can be found at
> + *http://www.gnu.org/
"SPDX-License-Identifier: GPL-2.0-or-later" is possibly a more brief and
modern way to say this in new code.
> + *
> + */
> +
> +/*
> + FileManifest
> +
> + A serializable set of filenames
> + each filename is associated with the package name that owns it
> +
> + Used when working with the install package file manifests in /etc/setup
> +*/
> +
> +#include <string>
> +#include <unordered_map>
This should be <map> as std::unordered_map is not used in the code.
> +#include <algorithm>
> +
> +class FileManifest: public std::map<std::string, std::string>
> +{
> +};
Is the new file filemanifest.h required at all? It could be reduced to
the following in install.cc:
#include <map>
...
typedef std::map<std::string, std::string> FileManifest;
// or more modern (C++11):
// using FileManifest = std::map<std::string, std::string>;
--
Regards,
Christian
[-- Attachment #2: check_for_conflicts.cc --]
[-- Type: text/plain, Size: 1450 bytes --]
#include <cstdio>
#include <map>
#include <string>
using FileManifest = std::multimap<std::string, std::string>;
int main()
{
FileManifest manifest;
// read from /etc/setup/*.lst.gz
const FileManifest installed {
{"/usr/bin/file11", "package1"}, // #1 package2
{"/usr/bin/file12", "package1"}, // #2 package3
{"/usr/bin/file21", "package2"},
{"/usr/bin/file22", "package2"}, // #3 package3, package4
{"/usr/bin/file11", "package2"} // #1 package1
};
manifest.insert(installed.begin(), installed.end());
// read from tar files to be installed
const FileManifest install {
{"/usr/bin/file31", "package3"},
{"/usr/bin/file12", "package3"}, // #2 package1
{"/usr/bin/file22", "package3"}, // #3 package2, package4
{"/usr/bin/file41", "package4"},
{"/usr/bin/file42", "package4"},
{"/usr/bin/file22", "package4"} // #3 package2, package3
};
manifest.insert(install.begin(), install.end());
for (auto i = manifest.cbegin(), end = manifest.cend(); i != end; ) {
auto j = i;
if (++j != end && j->first == i->first) {
std::printf("Packages");
j = i;
do
std::printf(" %s", j->second.c_str());
while (++j != end && j->first == i->first);
std::printf(" contain file %s\n", i->first.c_str());
}
//else
//std::printf("Package %s contains file %s\n",
// i->second.c_str(), i->first.c_str());
i = j;
}
return 0;
}
next prev parent reply other threads:[~2023-04-24 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 14:43 [PATCH setup 0/2] " Jon Turney
2023-04-23 14:43 ` [PATCH setup 1/2] Add underlying() method to io_stream class Jon Turney
2023-04-23 14:43 ` [PATCH setup 2/2] Detect filename collisions between packages Jon Turney
2023-04-24 16:26 ` Christian Franke [this message]
2023-04-27 16:11 ` Jon Turney
2023-04-27 17:20 ` Christian Franke
2023-04-24 16:46 ` [PATCH setup 0/2] " Corinna Vinschen
2023-04-24 18:16 ` Achim Gratz
2023-04-27 16:11 ` Jon Turney
2023-04-28 5:51 ` Brian Inglis
2023-04-30 18:25 ` Jon Turney
2023-05-04 4:14 ` Brian Inglis
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=d9404b60-a482-2b65-ec69-ec13a178b459@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).