Re: [Fedora-packaging] packaging Digest, Vol 123, Issue 12
by Denis Arnaud
Hi Antonio,
2015-05-21 14:00 GMT+02:00 <packaging-request(a)lists.fedoraproject.org>:
> Date: Wed, 20 May 2015 18:53:31 +0200
> From: Antonio Trande <anto.trande(a)gmail.com>
> Message-ID: <555CBC0B.1090201(a)gmail.com>
>
> Hi all.
>
> Do exist packaging guidelines for building boost-related C++ projects
> with 'bjam' utility ?
>
Note that you do not have to use bjam to compile Boost-related C++
projects. You can use your favorite build system, which are well supported
by the Boost RPM package, for instance CMake and GNU Autotools.
An example of a CMake-built package using Boost is SOCI:
https://apps.fedoraproject.org/packages/soci
Kind regards
Denis
8 years, 11 months
Schedule for Thursday's FPC Meeting (2015-05-21 16:00 UTC)
by James Antill
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2015-05-21 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
2015-05-21 09:00 Thu US/Pacific PDT
2015-05-21 12:00 Thu US/Eastern EDT
2015-05-21 16:00 Thu UTC <-
2015-05-21 17:00 Thu Europe/London BST
2015-05-21 18:00 Thu Europe/Paris CEST
2015-05-21 18:00 Thu Europe/Berlin CEST
2015-05-21 21:30 Thu Asia/Calcutta IST
------------------new day----------------------
2015-05-22 00:00 Fri Asia/Singapore SGT
2015-05-22 00:00 Fri Asia/Hong_Kong HKT
2015-05-22 01:00 Fri Asia/Tokyo JST
2015-05-22 02:00 Fri Australia/Brisbane EST
Links to all tickets below can be found at:
https://fedorahosted.org/fpc/report/13
= Followups =
#topic #281 New Python Macros for Easier Packaging
.fpc 281
https://fedorahosted.org/fpc/ticket/281
#topic #508 New GID for openstack-neutron
.fpc 508
https://fedorahosted.org/fpc/ticket/508
#topic #513 Use python -Es in shbang
.fpc 513
https://fedorahosted.org/fpc/ticket/513
= New business =
#topic #531 Discuss guidelines for use of weak dependencies
.fpc 531
https://fedorahosted.org/fpc/ticket/531
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
https://fedorahosted.org/fpc/report/13
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
8 years, 11 months
Compiling boost-related C++ projects
by Antonio Trande
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi all.
Do exist packaging guidelines for building boost-related C++ projects
with 'bjam' utility ?
Are there particular rules or packages already in Fedora built with
this method ?
Thanks.
- --
Antonio Trande
mailto: sagitter 'at' fedoraproject 'dot' org
http://fedoraos.wordpress.com/
https://fedoraproject.org/wiki/User:Sagitter
GPG Key: 0x565E653C
Check on https://keys.fedoraproject.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJVXLwLAAoJEF5tK7VWXmU8/oMH/jsuBbiE48RUQuDYslswGQgf
II03VWOxfHUGFJVWCLpMrBIn1zsxLk8WM6/saeQ/wGeVOSpZa80Lznnyxfx3Acxx
tQ82Inb8h5VeGZDJ3YSMBdpvIRHtotwMVLV7hYhkCH+xZn34QEVzTDq3Fz7bR/Vp
dhKzKFB2NPMEHut5CGaj+4yqoJZOSlhfRuk0iYT9SlvzV9rC9kZ4oK/tFM0DoYul
fAmUjs4K9wRU6XFNVp8cFpRLsVm3+4LiT9mhN3qa6NKpuB9///hyoT6H2Hq0hTIo
Jvhqh/zROh9BIRSlu7ajbvfeMSYXXkHTOAiYxsH2Ag8a4Vld81xpDhDM9yFfjJM=
=OxAo
-----END PGP SIGNATURE-----
8 years, 11 months
New Rpm-ecosystem Mailing List
by Florian Festi
Hi!
tl;td: Join at http://lists.rpm.org/mailman/listinfo/rpm-ecosystem if
your interested in any part of the rpm ecosystem.
While there are quite some mailing lists already that deal with the
different tools around and including rpm we realized that there is no
good place to discuss issues that involve multiple parts of (our own)
package handling stack even less so to stay in contact with other rpm
based solutions. To solve this we create a new mailing list:
rpm-ecosystem(a)lists.rpm.org
Normal user questions and development talk is supposed to stay on the
per project mailing lists. The new list is for questions like:
* How do other implementations handle specific problems?
* Is this new feature interesting for downstream distributions?
* How do the different packaging guidelines treat a special topic?
* Anyone there to support our demand for this new rpm feature?
And it is for topics like:
* Packaging guide lines
* RPM features
* Build systems and compose tools
* Dependency solvers, installers and updaters
* RPM based image creation / non rpm based updates for rpm
based distributions
In short: It is meant to bind the rpm universe together.
Join at http://lists.rpm.org/mailman/listinfo/rpm-ecosystem
Please forward this mail to anyone that might be interested - especially
to rpm related sub projects and groups.
Thanks!
Florian
--
Red Hat GmbH, http://www.de.redhat.com/ Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Charles Peters
8 years, 11 months
Summary/Minutes from today's FPC Meeting (2015-06-14 16:00 - 17:15 UTC)
by James Antill
======================
#fedora-meeting-1: fpc
======================
Meeting started by geppetto at 16:01:41 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-05-14/fpc.2015-05-...
.
Meeting summary
---------------
* Roll Call (geppetto, 16:01:41)
* Schedule (geppetto, 16:06:24)
* LINK:
https://lists.fedoraproject.org/pipermail/packaging/2015-May/010648.html
(geppetto, 16:06:28)
* #530 request copylib exception for dcraw.c (geppetto, 16:06:58)
* LINK: https://fedorahosted.org/fpc/ticket/530 (geppetto, 16:06:59)
* ACTION: Everything using it should add a bundled(dcraw), until it's
a true fork. (geppetto, 16:21:50)
* ACTION: It's way too big and messy to be classified as a copylib
though, any potential users should probably look at moving to libraw
(geppetto, 16:22:25)
* #528 Allow Mono 4.0 to be bootstrapped with monolite (geppetto,
16:22:39)
* LINK: https://fedorahosted.org/fpc/ticket/528 (geppetto, 16:22:40)
* ACTION: Reboostrap mono with monolite binaries (+1:7, 0:0, -1:0)
(geppetto, 16:25:01)
* #527 AppData for Application Addons (geppetto, 16:25:12)
* LINK: https://fedorahosted.org/fpc/ticket/527 (geppetto, 16:25:13)
* LINK:
https://fedoraproject.org/w/index.php?title=User%3AVondruch%
2FDraftAppDataGuidelines&diff=412575&oldid=412571
(geppetto, 16:25:57)
* ACTION: AppData for application Addons (+1:6, 0:0, -1:0) (geppetto,
16:37:46)
* Open Floor (geppetto, 16:39:12)
* #526 Mandatory python3 packaging when upstream supports python3
(geppetto, 16:58:57)
* ACTION: Mandatory python3 packaging when upstream supports python3
(+1:5, 0:0, -1:0) (geppetto, 16:59:54)
* Open Floor (geppetto, 17:00:10)
* LINK: https://github.com/fedora-python/packaging-guidelines/
(tibbs|w, 17:00:16)
* LINK: https://fedoraproject.org/wiki/User:Tibbs/BuildReqDraft
(tibbs|w, 17:04:19)
* #497 Clean up BuildRequires section; don't try to define the minimal
build env (geppetto, 17:04:30)
* LINK: https://fedoraproject.org/wiki/User:Tibbs/BuildReqDraft
(geppetto, 17:04:36)
* ACTION: Clean up BuildRequires section; don't try to define the
minimal build env (+1:5, 0:0, -1:0) (geppetto, 17:08:40)
* Open Floor (geppetto, 17:08:49)
Meeting ended at 17:15:32 UTC.
Action Items
------------
* Everything using it should add a bundled(dcraw), until it's a true
fork.
* It's way too big and messy to be classified as a copylib though, any
potential users should probably look at moving to libraw
* Reboostrap mono with monolite binaries (+1:7, 0:0, -1:0)
* AppData for application Addons (+1:6, 0:0, -1:0)
* Mandatory python3 packaging when upstream supports python3 (+1:5, 0:0,
-1:0)
* Clean up BuildRequires section; don't try to define the minimal build
env (+1:5, 0:0, -1:0)
Action Items, by person
-----------------------
* **UNASSIGNED**
* Everything using it should add a bundled(dcraw), until it's a true
fork.
* It's way too big and messy to be classified as a copylib though, any
potential users should probably look at moving to libraw
* Reboostrap mono with monolite binaries (+1:7, 0:0, -1:0)
* AppData for application Addons (+1:6, 0:0, -1:0)
* Mandatory python3 packaging when upstream supports python3 (+1:5,
0:0, -1:0)
* Clean up BuildRequires section; don't try to define the minimal
build env (+1:5, 0:0, -1:0)
People Present (lines said)
---------------------------
* tibbs|w (117)
* geppetto (95)
* mbooth (18)
* zodbot (17)
* limburgher (17)
* tomspur (13)
* orionp (9)
* Rathann (5)
* tibbs (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
8 years, 11 months
Proposal: Remove BuildRequires: exceptions from the guidelines
by Jason L Tibbitts III
TL;DR: There's a proposal for nuking the list of BuildRequires
exceptions from the packaging guidelines.
Important note: this is just an idea. We're not currently changing the
guidelines based on this. Nothing is set in stone. It may end up that
nothing happens. Don't panic.
A couple of times recently, people have floated proposals to the FPC
about removing certain things from the buildroot. (Specifically, perl
and gcc*.) And the bottom line for these is that while FPC tries to
maintain a list of BuildRequires: exceptions, this is really up to
releng and whatever rpm happens to pull in at any particular time.
This means that whatever list FPC maintains, it's going to get outdated
eventually, and giving packagers the idea that they don't have to
actually specify all of their dependencies restricts what releng can do
and, perhaps, what dependencies the RPM package can drop without
breaking builds.
So, the generally stated proposal:
I would like to get FPC out of the business of specifying this list of
exceptions, and instead just indicate that packagers should completely
specify their dependencies.
My specific proposal can be seen in
https://fedorahosted.org/fpc/ticket/497; the draft is at
https://fedoraproject.org/wiki/User:Tibbs/BuildReqDraft2. You can use
the history tab to see the differences between that and the current
guidelines.
Now, the real issue is in what packagers can depend upon. Obviously you
have RPM and an environment necessary to build a package (which means
you have to have a shell to execute the scripts that make up the RPM
sections, and redhat-rpm-config, and whatever RPM happens to use to
execute %patch, which I guess could be some internal library if the RPM
devs wanted). But what else? That's the open question.
The draft currently says:
---
You may assume that you have everything necessary for RPM to function
and process your spec file (so of course RPM is present, along with
redhat-rpm-config and what is necessary for RPM to apply patches, unpack
archives, and run the shell scripts which make up the spec file
sections.) You should not assume any other packages are present, as RPM
dependencies and anything brought into the buildroot by the build system
may change over time.
---
Honestly, I'm not completely satisfied with that but I can't come up
with anything better. Polite discussion is welcomed and encouraged.
- J<
8 years, 11 months
Summary/Minutes from today's FPC Meeting (2015-05-07 16:00 - 17:20 UTC)
by James Antill
======================
#fedora-meeting-1: fpc
======================
Meeting started by geppetto at 16:01:51 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2015-05-07/fpc.2015-05-...
.
Meeting summary
---------------
* Roll Call (geppetto, 16:01:51)
* Schedule (geppetto, 16:09:31)
* LINK:
https://lists.fedoraproject.org/pipermail/packaging/2015-May/010638.html
(geppetto, 16:09:36)
* #480 Packaging guidelines for consistent PKCS#11 usage (geppetto,
16:10:04)
* LINK: https://fedorahosted.org/fpc/ticket/480 (geppetto, 16:10:04)
* LINK: https://bugzilla.redhat.com/showdependencytree.cgi?id=PKCS11
(dwmw2, 16:22:30)
* ACTION: Packaging guidelines for consistent PKCS#11 usage (+1:5,
0:0, -1:0) (geppetto, 16:34:33)
* #524 static UID for ceph (geppetto, 16:35:34)
* LINK: https://fedorahosted.org/fpc/ticket/524 (geppetto, 16:35:40)
* ACTION: static UID for Ceph (+1:5, 0:0, -1:0) (geppetto, 16:42:27)
* #520 [Guidelines Draft] Per-Product Configuration Defaults v2
(geppetto, 16:42:42)
* LINK: https://fedorahosted.org/fpc/ticket/520 (geppetto, 16:42:42)
* #513 Use python -Es in shbang (geppetto, 16:44:07)
* LINK: https://fedorahosted.org/fpc/ticket/513 (geppetto, 16:44:07)
* #508 New GID for openstack-neutron (geppetto, 16:44:50)
* LINK: https://fedorahosted.org/fpc/ticket/508 (geppetto, 16:44:50)
* #281 New Python Macros for Easier Packaging (geppetto, 16:49:35)
* LINK: https://fedorahosted.org/fpc/ticket/281 (geppetto, 16:49:35)
* LINK: https://fedoraproject.org/wiki/Changes/Python_3_as_Default
(tibbs|w, 16:59:54)
* Open Floor (geppetto, 17:07:33)
Meeting ended at 17:21:03 UTC.
Action Items
------------
* Packaging guidelines for consistent PKCS#11 usage (+1:5, 0:0, -1:0)
* static UID for Ceph (+1:5, 0:0, -1:0)
Action Items, by person
-----------------------
* **UNASSIGNED**
* Packaging guidelines for consistent PKCS#11 usage (+1:5, 0:0, -1:0)
* static UID for Ceph (+1:5, 0:0, -1:0)
People Present (lines said)
---------------------------
* geppetto (91)
* tibbs|w (88)
* dwmw2 (22)
* zodbot (14)
* Rathann|Mobile (11)
* mbooth (7)
* orionp (6)
* sgallagh (6)
* rdieter (5)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
8 years, 11 months