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=0OkbusN82HFd1oNnw69f0iu3eBpPKRznF7dq0rRMUsg=; b=Xdrm/WT7h4GuXvvrJ634srrR5lj+3eyM+6wp1LMEQZSdSOTIoRFGs3CyqWFBA9GOz6 +fzseF375TpEXpdJj9E14XVpHHHDpom492xAuL0YT0XRrxgvG7U++gCneBWuvCpV9fFL M2wMcTT5kyvX4hM9EI0URjR5HvpDylcz2yCn+beTYvUgFZqeSI+kCRvAKzoc3n6N0dKR lJwEjm0wKk3TnKjut9f2MumQAfbhbUOoJ1SPsJe9lnsFOzKkkvCIuqdt2fe5zkN1Tog8 gtoRfQmNCejRTFPw8eBl04Mo4V+nkhdbKkgOWuQm69+VUKOx5nniz4ghUtTVKaSQc0h4 skVA== 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=0OkbusN82HFd1oNnw69f0iu3eBpPKRznF7dq0rRMUsg=; b=DvbaqFm/oK8toh60sM4n5UEybYoHCQNVdnu3J1VYZL9dBoXsUo0LOHG1P/lDaitb+C WizChr0TD/SywuWL+DUF5TyApnAxWwu6TSuXFtmJYDuwKPKMztPfqBQaoCv74K7mjV0t I2Mxsoth6/s8UPiLhnhS4tm1z52MGLwtXxM9iVAYe4p30Mwg7pyNWDsEXECXlAvepSrV QJmo08Y6kQ9AcjSSHYWZwkzTgwp/uxbeHNSI8hwfFCX+sMszBqI5K6McPvP6DDhWF4GH hrUdzeXtvFgkit51cZDzxKn4kadHADV6hyw85Ab6iDpee8P3v6mTDIvN9/d8PsqMEPzV /jzw== X-Gm-Message-State: AE9vXwOJ2A9r23mIKsfM7MeeXHo0lrYKc2twPlYES2wnVJFfCQ3sdCs+2+JUAOa3PDNyLQ== X-Received: by 10.25.148.142 with SMTP id w136mr4791753lfd.210.1473005477388; Sun, 04 Sep 2016 09:11:17 -0700 (PDT) Sender: Ivan Zakharyaschev Date: Sun, 4 Sep 2016 19:11: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@gmail.com, 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 16:11:19 -0000 Archived-At: List-Archive: On Sun, 4 Sep 2016, Neal Gompa wrote: > On Sun, Sep 4, 2016 at 7:28 AM, Ivan Zakharyaschev wrote: >>> package in ALT Linux, and I was wondering if you guys had contemplated >>> upgrading from rpm 4.0.4 to rpm 4.13? >> >> >> glebfm@ and legion@ are busy now with this. >> https://lists.altlinux.org/pipermail/devel/2016-July/201603.html >> >> They could give most details about this process. >> >> 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.) >> > > I'm sorry, I'm not too familiar with ALT's rpm setup, what is rpm-install? Simply, there is the rpm-build part of RPM which is used to create files of RPM format; and the "other" part, the essential one, the tool of the administrator which takes an RPM file and installs it, etc. To distinguish this basic part from rpm-build, we have been calling it rpm-install sometimes. (Theoretically, they are not tightly connected, and any other tool could be used instead of the standard rpm-build to produce RPM files if you target a distro which uses rpm to install packages, to control their dependencies etc. So, if someone thinks that the language of spec-files is ugly--like me--one can think about creating an alternative tool to describe the packages in another language, but still submit them to the same distro; for example, I'm interested in the way nix packages are done, and sometimes I'm thinking about various proxies like a tool to build an RPM package from nix rules, but also other kinds of proxies, in order to make the current work in ALT Sisyphus and in NixOS closer and more suitable for exchanging packages, switching the sources of the "specs".) >> [1] https://www.altlinux.org/Rpm-4.13 >>> like to see the ALT Linux rpm maintainer team be involved in upstream >>> rpm.org development, as I'm sure your perspective would be valuable to >>> ensure a vibrant ecosystem around rpm. >> >> >> As said, there are a few ALT-specific nice, important and non-trivial >> features in RPM, which would always require maintaining a separate fork >> unless they are taken up by another RPM project, say, the rpm-4.13 project. >> Then the forces could be joined. > If any of you guys who know about the extra features of your variant > of rpm can talk about them, it'd be great if they could bring them up > in the rpm-ecosystem mailing list[3] to propose for them to be merged > upstream into the rpm.org codebase. Florian Festi (the manager of the Thanks for the links! Let's look forward. One more small comment from me: in a sense, it would be a good moment now to merge some patches right after Gleb has rebased the features onto 4.13, so that there is no delta. If you are interested in the patches, of course, you can have a look in the Git repository in the linked task (in one of the linked posts) and ask the authors any questions, but I'd suggest to wait until it is committed to ALT Sisyphus; then, it would be in a more finalized state. http://git.altlinux.org/tasks/166699/ > rpm project) is always interested in receiving patches for new > features and such. Patches are accepted via rpm-maint mailing list[4] > or GitHub[5]. Discussions can also occur on IRC on Freenode in > #rpm-ecosystem and #rpm.org. Best regards, Ivan