User contributions for Majioa
12 December 2023
- 15:2415:24, 12 December 2023 diff hist +1 Template:DraftPolicy No edit summary current
- 15:2215:22, 12 December 2023 diff hist +644 N Template:DraftPolicy Created page with "{| style="border:1px solid #AAA; background:#F9F9F9; width:200px; margin: 0 0 1em 1em; padding:.2em; text-align:center; float: right;" class=noprint |- | Image:Stub.png |- | '''Sisyphus Policy draft''' |- |Authur(s) — {{{responsible}}} |- |{{#if: {{{discussion_link|}}}|[{{{discussion_link}}} Discussion in devel@]}} |- |{{#if: {{{discussion_since|}}}|Discussed from {{{discussion_since}}} }} |- |{{#if: {{{metabug|}}}|Policy violations monitored by: {{{metabug}}} }} |..."
- 15:1515:15, 12 December 2023 diff hist +21 Ruby/Usage No edit summary
- 15:0815:08, 12 December 2023 diff hist +23 Ruby No edit summary current
- 15:0715:07, 12 December 2023 diff hist +39 Ruby/Usage →Usage
- 15:0615:06, 12 December 2023 diff hist +134 Ruby/Usage →Usage
- 15:0415:04, 12 December 2023 diff hist +748 N Ruby/Usage Created page with "== Usage == You have to use system ruby generally for several purposes, so you have to: # use application, which strictly requires ruby, like: [https://packages.altlinux.org/ru/sisyphus/srpms/foreman/specfiles foreman], [https://packages.altlinux.org/ru/sisyphus/srpms/gem-alexandria-book-collection-manager/specfiles gem-alexandria-book-collection-manager]; # use ruby for development only purposes on your local machine; Usage system ruby for production cases is UNSUPPOR..."
- 14:5014:50, 12 December 2023 diff hist −7 Ruby/Policy 2.0 No edit summary
- 14:4714:47, 12 December 2023 diff hist +1,364 Ruby/Policy 2.0 →Ruby Policy
- 14:1814:18, 12 December 2023 diff hist +99 Ruby No edit summary
- 14:1614:16, 12 December 2023 diff hist +315 N Ruby Created page with "It is ruby related pages for active ALT Distributions, please follow the related chapter: #. Ruby/Introduction #. Ruby/Comparison #. Ruby/Packaging Notes #. Ruby/Typical spec #. Ruby/Testing #. Ruby/Migration #. Ruby/Automatization #. Ruby/Policy (obsoleted) #. Ruby/Policy 2.0"
- 14:1114:11, 12 December 2023 diff hist −14,421 Ruby/Policy 2.0 Replaced content with "{{DraftPolicy |responsible=Малъ Скрылевъ |discussion_link=https://lists.altlinux.org/pipermail/devel/2019-February/206679.html |discussion_since=05.02.2019 }} == Ruby Policy == __TOC__ '''''Rules for ruby module and application packages''''' Category:Ruby" Tag: Replaced
- 14:1114:11, 12 December 2023 diff hist +1,519 N Ruby/Automatization Created page with "== Automatization == To automatize the watch and update the ruby-based packages the gem '''gem-rubobot''' shall be used, to accomplish the following functions: * execute the watch for new ruby-based package versions and notify the subscribers about their appearance on '''rubygems.org'''; * execute the watch for new version of ruby language, notify the subscribers about their appearance; * make an integrity control over the gem subsystem in Sisyphus, by the aim of the sp..." current
- 14:1014:10, 12 December 2023 diff hist +1,425 N Ruby/Migration Created page with "== This scheme migration rules == # all the '''Requires''' dependencies for all the subpackages are determined automatically, so that all the dependencies of suck kind must be rejected; # '''BuildRequires''' dependencies for the package in case when testing shell be executed (see ''%check'' section), or when it is really necessary to do, must be explicitly defined, and can be got by the '''setup.rb''' application; # when the package has been renamed, it is required to e..." current
- 14:0714:07, 12 December 2023 diff hist +537 N Ruby/Testing Created page with "== Testing == Testing of the ruby based packages can be carried out by the '''gem-setup''' package that defines and runs required to the testing of the packages specs, which are usually resided in the ''spec''/''test''/''features'' folders. The required the execute that test procedure gems are defined in the '''Gemspec'''/'''.gemspec''' pair. In order to enable the testing procedure we need to explicitly decleare the required gems in the package '''.spec''', for example..." current
- 14:0614:06, 12 December 2023 diff hist +479 N Ruby/Typical spec Created page with "== Typical .spec == To fix an old or broken packages, along with the to create new ones, the maintainer can use the following typical spec file which is show here. The '''%ruby_build''' macro is being expanded to call to ''setup.rb'' install action, with fix to shebang line with auto param as ''--shebang=auto'' This forces to automatically detect ruby interpreter installation path and replace all the ruby executables with the proper shebang l..." current
- 14:0514:05, 12 December 2023 diff hist +5,061 N Ruby/Packaging Notes Created page with "== Packaging notes == === The 'ruby' package === In the system there is the only ''libruby'' library, with a single set of the ''stdlibs'' modules. When a new version of the ''libruby'' package has been built, all the ''stdlibs'' modules is rebuilt also, along with all gems that contain dynamically loaded ''.so'' libraries that conforms to the new version of ''libruby'', or where the ''Gemfile''/''.gemspec'' file pair contains explicit requirement to the ruby version i..." current
- 14:0214:02, 12 December 2023 diff hist +1,877 N Ruby/Comparison Created page with "== Comparison to the previous policy == Strictly speaking the approach with dependencies search over the only '''require''' calls to the modern time is significantly restricted by the following points: * this method calls are not always exactly detecting the real dependencies list for gems, and increasingly for ''Gemfile''-based projects, insofar as there may be non-mandatory calls to ''require'' in the code, which are framed in the ''begin-end'' code th..." current
- 14:0114:01, 12 December 2023 diff hist −79 Ruby/Introduction →Ruby and modularity: renove note current
- 14:0014:00, 12 December 2023 diff hist +278 Ruby/Introduction update out changes
