Print

Print


@bbockelm I have to say that I don't like the idea that the rpm naming convention will work reliably only for master and stable branches, and will give random results for devel branches. If we cannot do something that works reliably for every one better not do it.

I suppose we could simply add a parameter to the makesrpm.sh script, that when present is used as the the Version in xrootd.spec. This way the dirty scripting would be moved to the build system that chooses to use this feature. Also, this would allow for including the build number in the version, which might be handy sometimes.

I do agree that a policy that every release tagged in a stable brunch gets merged back to master, would be useful.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@simonmichal in #521: @bbockelm I have to say that I don't like the idea that the rpm naming convention will work reliably only for master and stable branches, and will give random results for devel branches. If we cannot do something that works reliably for every one better not do it.\r\n\r\nI suppose we could simply add a parameter to the makesrpm.sh script, that when present is used as the the Version in xrootd.spec. This way the dirty scripting would be moved to the build system that chooses to use this feature. Also, this would allow for including the build number in the version, which might be handy sometimes.\r\n\r\nI do agree that a policy that every release tagged in a stable brunch gets merged back to master, would be useful.\r\n\r\n\r\n\r\n"}],"action":{"name":"View Pull Request","url":"https://github.com/xrootd/xrootd/pull/521#issuecomment-304923759"}}}

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1