packaging December 2017

packaging@lists.fedoraproject.org

21 participants
17 discussions

Re: Proposed Fedora packaging guideline: Forge-hosted projects packaging automation
by nicolas.mailhot＠laposte.net 09 Dec '17

09 Dec '17

De: "Zbigniew Jędrzejewski-Szmek" > Impressive! I just tested this on some random package using github and > everything works great. Thanks for the nice feedback > Would it be possible to drop the requirement to have "/" at the end > of a github URL? I think it's natural to paste the URL without the > trailing slash... Not having to handle special cases was easier for me, but ok done, the macro is now less pedantic. > Your instructions say "just copy the file into /usr/lib/rpm/macros.d", > suggesting that the name can by anything, but I think it has to start > with "macros.". You're right, it's documented now. > Wouldn't it be better to recommend %autosetup instead of %setup? > It's one less thing to change if patches are added. I don't have a good history with %autosetup :) It tends to hate the patches I produce. OTOH it would be nice if the macro could adjust %setup to mean %setup -n %{archivename} when necessary, but I couldn't figure how to do it cleanly. > add a text like > "See https://fedoraproject.org/wiki/Packaging:Versioning how to adjust > Release tag for pre-/post- release commits.". Done, thank you for the review. Regards, -- Nicolas Mailhot

1 0

Are commas allowed in BuildRequires ?
by Marwan Rabbâa 07 Dec '17

07 Dec '17

Hello, I am creating a tool to automate RPM build process (at least reduce maintenance process). I have found a wonderful (for my tests) RPM spec => http://pkgs.fedoraproject.org/cgit/rpms/git.git/tree/git.spec According to section 10.1 in http://rpm5.org/docs/rpm-guide.pdf commas are not allowed in BuildRequires, but I have found ****************************************** BuildRequires: perl(Error), perl(ExtUtils::MakeMaker) ****************************************** How can I help for this ? Regards,

6 12

Re: Package naming question
by Björn Persson 05 Dec '17

05 Dec '17

"Tomasz Torcz" <tomek(a)pipebreaker.pl> wrote: > December 4, 2017 11:21 PM, "Björn Persson" <Bjorn(a)xn--rombobjrn-67a.se> wrote: > > Is your package meant to be parallel-installable with the parallel > > package? If so, what is the program called, since /usr/bin/parallel is > > taken? Or is it meant to conflict with GNU Parallel? > > We have solved this years ago. man alternatives Even if Alternatives is used the actual executable file must still have another pathname. It might be a good idea to coordinate that name with the package name. Björn Persson

1 0

Re: Package naming question
by Jun Aruga 05 Dec '17

05 Dec '17

Perl: perl-foo Python: python-foo NodeJs (NPM): nodejs-foo Ruby: rubygem-foo R: R-foo PHP: php-foo Golang: golang-foo The prefix pattern "rust-parallel" looks better. Jun On Mon, Dec 4, 2017 at 3:45 PM, Zbigniew Jędrzejewski-Szmek < zbyszek(a)in.waw.pl> wrote: > On Mon, Dec 04, 2017 at 09:19:26AM -0500, Gerald Henriksen wrote: > > On Mon, 04 Dec 2017 10:20:13 +0100, you wrote: > > > > >I would like to hear opinion of other packagers about naming. We have > > >`parallel` utility implemented in Rust which is drop-in replacement for > GNU > > >parallel. I was thinking how to name package and how people would > expect it to > > >be named. So far options are: > > > > > >* rust-parallel > > >* parallel-rust > > >* parallel-rs > > > > > >I dislike first one because it is not ending up in completion while > second and > > >third are quite good. > > > > To me the second and third make it look like the package is part of > > the existing parallel package - perhaps rust bindings to parallel - > > and not an entirely different program. > > > > In other words, I could see people install parallel-rust because "it > > must be part of the parallel package" based on its naming and not > > realize it is an entirely different program doing the same thing. > > Yes. In other words, the problem started when somebody decided to > reimplement a well-known existing package in a different language without > changing the name. It seems like the right solution is to ask the > rust-parallel folks to rename their project instead of squatting on an > existing name. > > Zbyszek > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org > -- Jun Aruga jaruga(a)redhat.com IRC: jaruga, Office: TPB(Technology Park Brno) Building C 1F, Brno, Czech Republic

3 3

Package naming question
by Igor Gnatenko 04 Dec '17

04 Dec '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, I would like to hear opinion of other packagers about naming. We have `parallel` utility implemented in Rust which is drop-in replacement for GNU parallel. I was thinking how to name package and how people would expect it to be named. So far options are: * rust-parallel * parallel-rust * parallel-rs I dislike first one because it is not ending up in completion while second and third are quite good. Thoughts? - -- - -Igor Gnatenko -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlolE00ACgkQaVcUvRu8 X0zcDg/+J4jaboaEmySwsgHiSNDfVqazoxrcZDp0abS8wRO9jSxXCPU0K/MpBgtg W3LnJOkEhr4WjRtwoC4MmvZf99sfBo4q6ATfd2hOg0WeYkwP36Fu9lVZUAEP6V0E zVNp44UCuxJNU9IxUvop4XVJOTmaF0Be3pGrJ2LRliZkIgJgzVwOk8pkv/eO1iwp Y5j2VK7Wjs1Z2/tuL6/u02GqZOpD/0NE145awQUp2PFNwIwYeP70UZ5OjoqdLPNO LAWybGPSuoaLN7xT7F3FFvqUBhU6Ypsnc2trd01DyJ81v8ITxeAxZpyMy/jLsoyU 0RyP5UJyzI/joGNLHDQimmBnBH3SOcVr68Sx2TIMLxmsyCFaGmv+ehZlTkRWocnM QWc0fKOD5FC9W7NY21NOCADG6tuIjj+n8Ncw27gbZ0gexbq/drcq9J7aaiKZ0USf HA7iKya6OiuSKI2GAzKGMcBzp3GKkcUl+3NSBOw2bB/fF1NneXJDL4FkQVhvC+Ta G9Hmz3MC+f/amozta7y+pPAzswf5yzArc1Lcw/HWx3QG3S/DAlR+fnJntf+Rgz6I KRYyasi+RLUizzxBnlOXsi3PM3ppErHXmCfewyyhNup0T+DQsW3Na9/q6nWea/1+ I2WA3kZEmoYHEZM5d3r4I3vPliz0QXJQjNkpicqCxg+A85CBH44= =TEXI -----END PGP SIGNATURE-----

3 2

dist macro considering bootstrapping
by Jun Aruga 04 Dec '17

04 Dec '17

Hi, 11 days ago, I suggested to change %dist marco definition. This change is inevitable if people are working on a module (modularity) that needs bootstrapping in the module build. [RFE] Update dist macro considering bootstrapping. https://pagure.io/fedora-release/pull-request/120 Right now there is no response. What is a better way or workflow to suggest this? -- Jun

1 0

Re: Package naming question
by Igor Gnatenko 04 Dec '17

04 Dec '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, 2017-12-04 at 10:50 +0100, Adam Samalik wrote: > What about an analogy with 'createrepo'? We have: > > * createrepo > * createrepo_c That's only because createrepo_c is upstream name. > Using this same analogy: > > * parallel_rust > * parallel_rs This is really worst user experience. - -- - -Igor Gnatenko -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlolHQEACgkQaVcUvRu8 X0yaJQ/+L9WLnv2YtiRmndKs5x08R5pBb9wE6rqMCVKcdig7zvQindrJctBv7+aO DfpqGCCsYk54uVsv3vhoHWHoA4IwYm/AvkAyI52b9/wo0AxXvZikS0VwbqPNUuAP 5thG/ojTCJF7fpYHQzaoI5SIIPLyHPFksKWsYfsp08tnZ2Y8OpJeBDDE+prP0I73 +zLD376JpfqYm7JEVUuZqIWNRrks8PlJqxzVA0yc+Py0h5eixA+ehWUDwZrvoHV6 Vbf8taUKVwOBtH7WlWS+Eq6GDmk5CKDdEoq3Qvrec6vr8LSFKi2mWN6Jipqry8dc psokbiJhYG/sBGZgdaZvea4lCHW7isQHKiB4yAT0WvodphNBASfmGkQH6gKyVCL+ eeToRMbFEX0jEj5Y58qJW5alY7MWGJrgLjTaQd8hovHV0e0Xs3M2PLecIqbt2+a3 aZnpDa/YvcaA6zl1D6wED7ugumKdznP5iIeNMJU6gClfV48+Ox/ho4U4ABE9plle 0RAWHoHjppWvbBdhWINq1w16RI2+HqCCKcnBV9mW3znr01/9F0H7OZ3Wi99YKYs6 EiftkxYrGE1xRXyTSbk8L4EXiTDZxglBtWJXGUhLekAx9wMlYYb9Vh6cx8GJOyVU bcvQfhLzdlh85hKiXM4hRXnKaqtdfpZ4e7U6pM5SK574WP+Osoc= =zzi0 -----END PGP SIGNATURE-----

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

packaging December 2017