Debian Codegraph @

django_mailman3/tests/testdata/pipermail_nextpart.txt

raw
1 From vondruch at redhat.com Tue Jul 10 11:29:44 2012
2 From: vondruch at redhat.com (=?ISO-8859-2?Q?V=EDt_Ondruch?=)
3 Date: Tue, 10 Jul 2012 13:29:44 +0200
4 Subject: [Fedora-packaging] RPM macros
5 Message-ID: <[email protected]>
6
7 Hi,
8
9 I noticed that in revised haskell guidelines [1], there is mentioned the
10 ghc-rpm-macros package, which provides macros.ghc file, which in turns
11 provides some useful macros for packaging of Haskell packages. In Ruby,
12 we provide similar macro files in ruby-devel and rubygems-devel
13 subpackages respectively. Perl has their macros directly in the rpm
14 package itself.
15
16 This seems to be a bit inconsistent to me. So my question is: shouldn't
17 we standardize some best practices with regards of RPM macros? For
18 example for Ruby, we placed the macros into -devel subpackages, because
19 we believe that it is just development dependency. Any opinions?
20
21
22 Vit
23
24 -------------- next part --------------
25 A non-text attachment was scrubbed...
26 Name: signature.asc
27 Type: application/pgp-signature
28 Size: 190 bytes
29 Desc: This is a digitally signed message part.
30 URL: <http://lists.fedoraproject.org/pipermail/packaging/attachments/20120713/2377d1ee/attachment.sig>