Removing myself as I have moved away from Solus. Thanks for all you do guys - had some system freezes that happened fairly often, unfortunate but I needed to move to something more stable.

In D6888#133060, @Jacalz wrote:

Tested this now as I needed jekyll for a project.
I noticed that rundeps are missing, for example missing the whole Ruby package that makes it actually run...

@livingsilver94 Gotcha, that makes more sense. Thanks!

Remove un-necessary files such as empty dirs and LICENSE and README through install key
Remove abi_used_libs

@livingsilver94 Thanks for the info and suggestion! Went ahead and removed it. Is there something I can set in the package.yml to strip out files or folders that are not needed?

Remove README and LICENSE in the pspec xml

@livingsilver94 Any updates on this? Is there anything else I need to do?

I'm abandoning this because Jekyll was updated in a way that it does not require this to be in our repository. See https://dev.getsol.us/D6888#114662 for more details.

I'm abandoning this because Jekyll was updated in a way that it does not require this to be in our repository. See https://dev.getsol.us/D6888#114662 for more details.

@livingsilver94 Great news! Everything works perfectly on Jekyll 4.0.0. I guess they updated their files or something to run the bundler (installs all of the dependencies) when making a new jekyll project, so everything checks out! I'm going to remove my other packages that were deps of this so I can focus purely on Jekyll.

Update Jekyll to 4.0.0

@livingsilver94 Hi there, sorry this has not been updated in awhile. I recently found a new job and had some issues with moving. Now that I am all settled in -

Update package.yml to my most current implementation

@davidjharder Thank you! That helps a lot.

@livingsilver94 Jekyll has quite a few runtime deps, here's the rubygem link to view them: https://rubygems.org/gems/jekyll.

@Girtablulu After doing some testing I've found that the .gemspec fails on https://github.com/jekyll/jekyll/blob/master/jekyll.gemspec#L17.

@livingsilver94 Gotcha, that's what I was thinking but just wanted to check. Thanks!

@Girtablulu Okay, understood. Apologies if it seemed like I was trying to force a change or anything - just looking for information. :)

@Girtablulu Hi there, new package maintainer here. I'm wondering how to access (or what I need to do to obtain) an older version of this package - specifically 0.9.5. I need it for Jekyll - https://dev.getsol.us/D6888. Thanks!

@livingsilver94 Does it make more sense to name this package ruby-jekyll to conform with other ruby gem packages on Solus?

Change license section to list correctly.

Update rouge to 3.8.0

Oops...sorry about that. :/
I just figured since they were each separate and might be needed for other packages that requests were needed for correct tracking.

Add maintainer file (for real this time).

Add maintainer file.

Add maintainer file.

Update package name to ruby-rouge

Update package name to ruby-safe_yaml

https://dev.getsol.us/D6895

https://dev.getsol.us/D6894

@livingsilver94 Hi there, thanks for the info! I've been trying to install and test - looks like Jekyll requires some additional gems in order to function correctly. Would it make sense to make Solus packages for these deps?

Add maintainer file and remove setup phase from package.yml

In D6888#108877, @livingsilver94 wrote:

Thanks for the patch!
Please reopen T6492 so that it can go through the proper task lifecycle, as you stepped in to be the maintainer of Jekyll. Also, be sure to include a file called MAINTAINERS.md with the following content:

This file is used to indicate responsibility for the maintenance of this package. Individuals on this list should be the sole modifiers of the package, excluding cases where the Solus Team may need to perform necessary rebuilds, upgrades, or security fixes. This list should not be used for any direct contact usage. If you believe this package requires a package update, follow documentation from https://getsol.us/articles/packaging/request-a-package-update/en/. In the event this package no longer becomes sufficiently maintained, Core Team reserves the right to request a new maintainer or remove this package from the repository.

- First and last name
  - IRC: you nickname on IRC
  - Email: your email address

Regarding your test plan, well, you surely test Jekyll on Solus, but you should be more specific about the tests you performed. It doesn't need to be elaborated, just a few steps will do it.

I am interested in becoming the maintainer for this package. I followed the guides on the support site and also the first video guide on YouTube.