From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on sa.local.altlinux.org X-Spam-Level: X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS autolearn=no autolearn_force=no version=3.4.1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=082JN+pXVoAXPfUcTfcbtJAaSrzjVz4VH3ISAzOnVAI=; b=QXygj15kBlKptSIof9ThKVl+eyEhCuMwkkv7TgjFJlkEwfmRRprEaPlj7gIU6UF+cp chmxN20EPKeNEksIHcLuMh3OMbQSmAQ4GYYOOWsYaNRh09umBMbBUonfXa4KOxTr6uRa 4vyNfIb4tuiX7cu9iwhVMWEprNZLlExTYDleyUVQVEpwmSfbSRDdwWFvbdyW0GOhBVKu M+2M1b7GdEQkM3yg65e/xFObgbFUn31tDaTBNxL3MLQqozaWcZqKYr1KV1SbOTyqgmwA u2TqN8Dw9ilj2aKtZR98u9g7lIf6vOxqo8+Xyr8E9ouQhWr2L6DazcxQamgvU/+K5AMh 68hg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:in-reply-to :message-id:references:user-agent:mime-version; bh=082JN+pXVoAXPfUcTfcbtJAaSrzjVz4VH3ISAzOnVAI=; b=ARj5UzFxSNrV3Wv3cvi9vEbEKv04ZH1spPUJoFO++GhutHbuAFDvwUQU/N0pgOQb3V 3BLstW2K1ghjQfJV9LNi4dCbzLiCFJ2Kw8Rf6KMEm7TzYYkhF1fP0Wl53yl0rXXKu15O rihdWLOGozTPi03P7M2A5ZUeH7usziCbFhZA+vi1fNOTuYju31OFEiCjehC+7xGHUt/n lAz+DkUo9QA0UPdZ0GAr9m3BDFSY4LbNCTTI6ElSevZl2GwfdV2F8cAkp+iaVXE1DGFd dtrVp8hZNPIgir9SmMOygAjVC25FTeIV0zJ+FFjjK02J9oYnvKKLBZoIVTs9b3ZuKlRY 3U6w== X-Gm-Message-State: AE9vXwOCMdqQy40QNvPWjPQNY0l2dPNaRdG4LXyA2eAL68fvtZVeI9830IybDCt2X8MI3w== X-Received: by 10.25.19.227 with SMTP id 96mr2310559lft.24.1473027376711; Sun, 04 Sep 2016 15:16:16 -0700 (PDT) Sender: Ivan Zakharyaschev Date: Mon, 5 Sep 2016 01:16:17 +0300 (MSK) From: Ivan Zakharyaschev X-X-Sender: imz@ovicaa.localdomain To: Neal Gompa In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (LFD 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Cc: rpm-ecosystem@lists.rpm.org, legion@altlinux.org, Alexey Tourbin , glebfm@altlinux.org, at@altlinux.org, community-en@lists.altlinux.org Subject: Re: [Comm-en] RPM in ALT Linux (4.0.4 vs 4.13) X-BeenThere: community-en@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: "ALT Linux users \(in English only\)" List-Id: "ALT Linux users \(in English only\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Sep 2016 22:16:19 -0000 Archived-At: List-Archive: On Sun, 4 Sep 2016, Neal Gompa wrote: >>>> The first thing to do on this way was to rebase many ALT's features[1] >>>> onto >>>> rpm(-install)-4.13. (Not yet features relevant for rpm-build.) >>>> [1] https://www.altlinux.org/Rpm-4.13 > I looked through the wiki page and also the git repository on ALT > Linux's gear for rpm-4.13[1], and there were some commits of concern: > > * git hash: 08677107ea8efb30099b05c0c9876e0cfdbd9799: Add support of > ALT Linux traditional posttrans filetriggers > - This commit is interesting because it's completely redundant. My > understanding is that the legacy file triggers implementation in ALT > Linux is derived from the original one developed by Mandriva. In I don't know enough about the history of it to tell this for sure. > Mageia, we've ported all of the Mandriva style file triggers over to > the system that's part of rpm 4.13, and we'd be happy to share with > you guys the newer versions of these and help you guys get up to speed > there. One issue is that the new rpm should be able to work with the old packages, published in the old distro branches, at least in order to enable an upgrade. Another one is that the rpm maintainer (like Gleb) can't rewrite the filetriggers in all the packages at once; rather he can provide the tool which implements the old and new features and wait for the maintainers of the packages who own the triggers to catch up; and ultimately, the old feature can be removed. I might be misunderstanding something about the mechanism. > * git hash: 61a1aaa2c0795f8bd564bdbef2b45cc4f44902ac: Write to syslog > about installed/removed packages > - Why exactly is this necessary? This isn't a huge deal, but wouldn't > apt handle this already? This also feels like it should be written as Some users invoke the bare rpm command. > an rpm plugin rather than be a mandatory part of rpm. Other resolvers > (like Yum/DNF and Zypper) do record this information already to some > form of database/log which is accessible at any time, so it would be > redundant in that case. What kind of plugin do you mean? > * git hash: 4487281b1ed93cc8a997adb56be51c33c52ebce9: Add > /usr/lib/rpm/macros.d/*, /etc/rpm/macros.d/* to macrofiles > - This one seems weird, as it disables the *.attr files and > eliminates the macros file name convention we've used in Fedora, > CentOS, Mageia, and openSUSE. I suspect this patch will remain > specific to ALT Linux. > > * git hash: 60ea90eeb0341c2f8c761133033cd3e015c082c7: Add scripts/find-package > - I understand why this exists (apt metadata doesn't include file > lists, so you can't resolve them). We have the same problem in Mageia > with urpmi's hdlist2 metadata. We have patches that alter rpm's own > find-requires script to work as you need it to so that you don't have > to disable the internal generators. I've attached them to this email, > with a "series" file to indicate the order in which the patches can be > applied. These patches were written by Thierry Vignaud of Mageia for > our rpm package to solve the same issue while leveraging the new > dependency generator framework. Mageia's implementation is not in the upstream, too, is it? Which implementation is better: the Mageia's one or the ALT's one? > I'll admit, I'm not really certain about many of the other ones... > Perhaps someone else here can take a deeper review of some of the > other patches and provide some feedback? > > Do you guys have an equivalent package to redhat-rpm-config[2] or > rpm-mageia-setup[3] which contains your vendor configuration for RPM? > It seems like some of this stuff (like the GROUPS file, macros, etc.) > belong there... As for build-stage macros, many of them are maintained in separate language/compiler specific small packages rpm-build-* or rpm-macros-*, like rpm-build-python, rpm-build-python3, etc. > [1]: http://git.altlinux.org/tasks/166699/gears/560/git?p=git;a=log > [2]: http://pkgs.fedoraproject.org/cgit/rpms/redhat-rpm-config.git/ > [3]: http://gitweb.mageia.org/software/rpm/rpm-setup/about/ Best regards, Ivan