Dear Packagers who are using Boostrapping logic for the cyclical dependency
Need your help to fix wrong Bootstrapping part in Guidelines.
This mail is long.
Sorry for that in advance.
You may be building the cyclical dependency packages by using a variable such as _with_bootstrap, need_bootstrap, bootstrap, enable_test, and etc..
For example, you may build with below ways for that, if you will use mock command.
```
$ mock -r fedora-rawhide-x86_64 --with=bootstrap *.src.rpm
=> _with_bootstrap can be used as --with=bootstrap
$ mock -r fedora-rawhide-x86_64 --define '_with_bootstrap 1' *.src.rpm
$ mock -r fedora-rawhide-x86_64 --define 'need_bootstrap 1' *.src.rpm
$ mock -r fedora-rawhide-x86_64 --define 'enable_test 1' *.src.rpm
...
```
Here is a document page to unify the Bootstrap logic.
You may know it.
https://fedoraproject.org/wiki/Packaging:Guidelines#Bootstrapping
However I found that below part in the page is wrong.
```
%{!?_with_bootstrap: %global bootstrap 1}
```
Because ..
If _with_bootstrap is not set from outside, bootstrap is 1
=> bootstrap is True/Enabled
if _with_bootstrap is set as 1 from outside, bootstrap's value is not set.
=> the value is empty if it is not declared in advance. It's a kind of 0. bootstrap is False/Disabled.
This situation is opposite meaning of "_with_bootstrap".
Below way not using negative operator `!?` is correct.
```
%{?_with_bootstrap: %global bootstrap 1}
```
The reason why I wrote this here is
I found that had already been reported 2 years ago for packaging committee, however it was closed without fixing.
https://pagure.io/packaging-committee/issue/509
I am not sure that why it is not admitted.
You may feel that it does not matter because you may edit the Bootstrapping logic in the RPM spec file manually.
But in my case, I am one of the people who use the Bootsrapping logic actively.
There are 89 RPM packages that constitutes Ruby on Rails 5.0.
To build Ruby on Rails 5.0 completely from scratch, I have to build the packages total 103 times considering bootstrap.
I am trying to build those packages automatically by a tool [1] with a configuration file [2] for Ruby on Rails.
It is important to fix it due to that.
Fortunately today another guy Vit created new ticket for that.
So, if YOU like this proposal, please comment in below page of the ticket or reply here.
It is helpful for us to move this huge rock. I really want to fix it.
"I like it." comment please.
=> https://pagure.io/packaging-committee/issue/684
Thank you for your help.
[1] https://github.com/sclorg/rpm-list-builder
[2] https://github.com/sclorg/rhscl-rebuild-recipes/blob/master/ror.yml
Kind regards,
Jun Aruga
======================
#fedora-meeting-1: fpc
======================
Meeting started by geppetto at 16:00:34 UTC. The full logs are
available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-10-26/fpc.2017-
10-26-16.00.log.html
.
Meeting summary
---------------
* Roll Call (geppetto, 16:00:34)
* Schedule (geppetto, 16:07:43)
* LINK:
https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject.org/message/2VLV4EIQWMZUDDDQWX7BCD2XMWJD4Q3T/
(geppetto, 16:07:45)
* #720 Easy way of changing/removing shebangs (geppetto, 16:09:10)
* Everyone seems happy with the general idea. (geppetto, 16:18:15)
* ACTION: ignatenkobrain A real draft we can vote on would be cool,
including an example or two (geppetto, 16:18:40)
* #559 Ban use of rich dependencies (geppetto, 16:20:22)
* ACTION: Allow rich deps. now infra. can handle them (+1:5, 0:0,
-1:0) (geppetto, 16:24:37)
* #705 Rust Packaging Guidelines (geppetto, 16:24:56)
* Just a note that this is unblocked now as rich deps. are fine in
infra. (geppetto, 16:26:36)
* IDEA: Add a note about rich deps to the EPEL guidelines (gholms,
16:26:40)
* #715 Separately building package documentation (geppetto, 16:28:34)
* LINK: https://pagure.io/packaging-committee/issue/715#comment-46745
8
speaks about test suites, but test suites don't produce any
artifacts, so bootstrapping guidelines apply here (Rathann,
16:36:18)
* Open Floor (geppetto, 16:59:37)
Meeting ended at 17:00:28 UTC.
Action Items
------------
* ignatenkobrain A real draft we can vote on would be cool, including
an
example or two
* Allow rich deps. now infra. can handle them (+1:5, 0:0, -1:0)
Action Items, by person
-----------------------
* ignatenkobrain
* ignatenkobrain A real draft we can vote on would be cool, including
an example or two
* **UNASSIGNED**
* Allow rich deps. now infra. can handle them (+1:5, 0:0, -1:0)
People Present (lines said)
---------------------------
* geppetto (70)
* tibbs (47)
* ignatenkobrain (34)
* Rathann (24)
* zodbot (13)
* contyk (10)
* tomspur (8)
* mbooth (3)
* gholms (2)
* jkurik (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
======================
#fedora-meeting-2: fpc
======================
Meeting started by geppetto at 17:00:53 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-2/2017-10-04/fpc.2017-10-0…
.
Meeting summary
---------------
* Schedule (geppetto, 17:09:56)
* LINK:
https://lists.fedoraproject.org/archives/list/packaging@lists.fedoraproject…
(geppetto, 17:10:26)
* #708 Allocating a static uid and gid for openvswitch (geppetto,
17:12:06)
* ACTION: We would need to know why it matters if the ID changes.
Backup software understand ID's can change, and so save names/etc.
(geppetto, 17:19:12)
* #710 Ruby packaging guidelines update (geppetto, 17:20:24)
* LINK:
https://fedoraproject.org/w/index.php?title=User%3AVondruch%
2FDraft_RubyGuidelines&diff=501566&oldid=500202
(geppetto, 17:21:07)
* ACTION: Q: Has the situation changed or should the admon/warning
change to reflect reality? (geppetto, 18:02:14)
* Open Floor (geppetto, 18:03:04)
Meeting ended at 18:05:19 UTC.
Action Items
------------
* We would need to know why it matters if the ID changes. Backup
software understand ID's can change, and so save names/etc.
* Q: Has the situation changed or should the admon/warning change to
reflect reality?
Action Items, by person
-----------------------
* **UNASSIGNED**
* We would need to know why it matters if the ID changes. Backup
software understand ID's can change, and so save names/etc.
* Q: Has the situation changed or should the admon/warning change to
reflect reality?
People Present (lines said)
---------------------------
* geppetto (40)
* mbooth (20)
* tomspur (19)
* Rathann (15)
* zodbot (14)
* pvalena (12)
* orionp (5)
* mboddu (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
Hi,
I'm packaging a PHP library [1] that is hosted on GitHub and has a
.gitattributes file that uses export-ignore to not make the test suite
directory part of the archive. As I want to run the unit tests in %check
during package build, this is a bit of a problem. I see two approaches:
1. ask upstream to remove test suite directory from .gitattributes
(probably won't work);
2. git clone the source and make my own archive after throwing away
.gitattributes
Maybe there is a better way I don't know about yet :-)
Thanks,
François
[1] https://github.com/paragonie/sodium_compat