Forum: Ruby-core [ruby-trunk - Feature #7708][Open] support for patches list

Issue #7708 has been reported by mpapis (Michal Papis).

----------------------------------------
Feature #7708: support for patches list
https://bugs.ruby-lang.org/issues/7708

Author: mpapis (Michal Papis)
Status: Open
Priority: Low
Assignee:
Category:
Target version:


Often as maintainer of RVM I have to work with multiple ruby patches, 
but it's hard to tell what patches were used for compiling ruby. As a 
temporary solution I have started using a file `patches.list` in the 
root of source and installation directory. It would be nice if Ruby 
would include this list also in RbConfig::CONFIG.

Here is example content of the file I have for ruby-1.9.3-p362:

    ruby-multilib
    segfault_fix_7629

If that would be implemented I could understand if it would be required 
the files to be URLs to online patches which can be easily downloaded 
and analyzed.

Issue #7708 has been updated by vo.x (Vit Ondruch).


Out of curiosity, how would you populate such list?
----------------------------------------
Feature #7708: support for patches list
https://bugs.ruby-lang.org/issues/7708#change-35453

Author: mpapis (Michal Papis)
Status: Open
Priority: Low
Assignee:
Category:
Target version:


Often as maintainer of RVM I have to work with multiple ruby patches, 
but it's hard to tell what patches were used for compiling ruby. As a 
temporary solution I have started using a file `patches.list` in the 
root of source and installation directory. It would be nice if Ruby 
would include this list also in RbConfig::CONFIG.

Here is example content of the file I have for ruby-1.9.3-p362:

    ruby-multilib
    segfault_fix_7629

If that would be implemented I could understand if it would be required 
the files to be URLs to online patches which can be easily downloaded 
and analyzed.

Issue #7708 has been updated by mpapis (Michal Papis).


this is code used in RVM to populate (and use) the list 
https://github.com/wayneeseguin/rvm/blob/825aa97e7...

it's all done before configuring ruby so the configure script could read 
the list and then make it available in RbConfig, of course this could be 
also easier done with environment variable like:

    RUBY_PATCHES="ruby-multilib:segfault_fix_7629"

It does not give any real functionality improvement but helps to 
identify if there were any patches to the ruby that is ran, it is useful 
with RVM binary rubies or with distribution provided rubies.

----------------------------------------
Feature #7708: support for patches list
https://bugs.ruby-lang.org/issues/7708#change-35454

Author: mpapis (Michal Papis)
Status: Open
Priority: Low
Assignee:
Category:
Target version:


Often as maintainer of RVM I have to work with multiple ruby patches, 
but it's hard to tell what patches were used for compiling ruby. As a 
temporary solution I have started using a file `patches.list` in the 
root of source and installation directory. It would be nice if Ruby 
would include this list also in RbConfig::CONFIG.

Here is example content of the file I have for ruby-1.9.3-p362:

    ruby-multilib
    segfault_fix_7629

If that would be implemented I could understand if it would be required 
the files to be URLs to online patches which can be easily downloaded 
and analyzed.

Issue #7708 has been updated by drbrain (Eric Hodel).

Target version set to next minor


----------------------------------------
Feature #7708: support for patches list
https://bugs.ruby-lang.org/issues/7708#change-35639

Author: mpapis (Michal Papis)
Status: Open
Priority: Low
Assignee:
Category:
Target version: next minor


Often as maintainer of RVM I have to work with multiple ruby patches, 
but it's hard to tell what patches were used for compiling ruby. As a 
temporary solution I have started using a file `patches.list` in the 
root of source and installation directory. It would be nice if Ruby 
would include this list also in RbConfig::CONFIG.

Here is example content of the file I have for ruby-1.9.3-p362:

    ruby-multilib
    segfault_fix_7629

If that would be implemented I could understand if it would be required 
the files to be URLs to online patches which can be easily downloaded 
and analyzed.