Le 26/01/2016 17:29, Jarek Polok a écrit : > Hi > > Thanks for comments ! > > Looking at your work with php55 .. I came up with > the following initial attempt at sclo packaging:
I think you have look at the mod_php package. Bad example ;) This one is really part of the PHP scl (and create some files in the httpd24 collection) I was thinking of packages in the sclo-php5x namespace Ex: https://github.com/sclorg-distgit/php-pecl-apfd Those package are really part of the php5# collections: not a separate collection, no meta package, built using php5#-build. The "sclo" prefix is only used in the package name: > > https://github.com/jaroslawp/sclo-mod_auth_mellon > > However .. I have some doubts about naming/packaging, > and would be glad to hear your comments: > > The SCL package (sclo-mod_auth_mellon.spec) > .. is basically useless (not used in this initial > attempt) since what the actual package > - mod_auth_mellon.spec - ships goes all into: > > /opt/rh/httpd24/root/[...] (httpd24 collection) > > of course that could be split ... rather artificially > into a part which would go into: > > /opt/sclo/mod_auth_mellon/root/[...] > > > but that would be little bit .. useless and > confusing since we would end up with sthg alike: > > > /opt/rh/httpd24/root/etc/httpd/conf.d/auth_mellon.conf > /opt/rh/httpd24/root/etc/httpd/conf.modules.d/10-auth_mellon.conf > /opt/rh/httpd24/root/run/mod_auth_mellon > /opt/rh/httpd24/root/usr/lib/tmpfiles.d/mod_auth_mellon.conf > /opt/rh/httpd24/root/usr/lib64/httpd/modules/mod_auth_mellon.so > > and: > > /opt/sclo/mod_auth_mellon/root/usr/libexec/mod_auth_mellon > /opt/sclo/mod_auth_mellon/root/usr/libexec/mod_auth_mellon/mellon_create_metadata.sh > > /opt/sclo/mod_auth_mellon/root/usr/share/doc/sclo-mod_auth_mellon-mod_auth_mellon-0.11.0 > > /opt/sclo/mod_auth_mellon/root/usr/share/doc/sclo-mod_auth_mellon-mod_auth_mellon-0.11.0/COPYING > > /opt/sclo/mod_auth_mellon/httpd24/root/usr/share/doc/sclo-mod_auth_mellon-mod_auth_mellon-0.11.0/NEWS > > /opt/slco/mod_auth_mellon/root/usr/share/doc/sclo-mod_auth_mellon-mod_auth_mellon-0.11.0/README I agree, this have mostly no sense > > I think it would be more natural/logical to package > having all files under /opt/rh/httpd24/ in this case > > and name the package: > > sclo-mod_auth_mellon0-mod_auth_mellon-X.Y > > (with a provide for httpd24-mod_auth_mellon) Yes, I think you can do something like this, using sclo-httpd24-mod_auth-mellon and providing httpd24-mod_auth-mellon Name: sclo-%{scl_prefix}mod_auth_mellon > ... but ... can we have a collection without the SCL > packages ... ? (-runtime/-scldevel/-build ..) Yes, but, this is not reaaly a collection, only a set of packages, extending a collection, from a different vendor. Remi P.S. notice the %scl_package_override macro seems missing in httpd24 collection, so you have to use _httpd24_* macro...:( > I think the case of mod_auth_mellon is little bit special > in the sense that this package is only an addon > for httpd24 - containing no standalone tools/libraries > - unlike php5X .. etc ...) > > > . I would be glad to hear your opinion > one the above ... > > Best > > Jarek > > __ > ------------------------------------------------------- > _ Jaroslaw_Polok ___________________ CERN - IT/CM/LCS _ > _ http://cern.ch/~jpolok ________ tel_+41_22_767_1834 _ > ______________________________________+41_75_411_9487 _ > > > _______________________________________________ > SCLorg mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/sclorg -- [email protected] | Senior Software Engineer / BaseOS / WebStack team GPG Key: 0x29F16A18 Fingerprint: 5A0E 6F54 D94D 5732 69EE E3FF 614A 6905 29F1 6A18 _______________________________________________ SCLorg mailing list [email protected] https://www.redhat.com/mailman/listinfo/sclorg
