Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add FreeBSD support #14

Open
wants to merge 7 commits into
base: master
Choose a base branch
from
Open

add FreeBSD support #14

wants to merge 7 commits into from

Conversation

olevole
Copy link

@olevole olevole commented Oct 14, 2018

changes for FreeBSD are trivial and mainly relate to
an alternative path to configuration and executable files.
So, the standard way for 3rd-party config files in FreeBSD:
/usr/local/etc{/rsnapshot}
and for binaries:
/usr/local
Also, define @cmd_rsnapshot in cron.erb via config_cmd_rsnapshot

@olevole
Copy link
Author

olevole commented Oct 14, 2018

Tested on:
FreeBSD 11
FreeBSD 12

If you plan to expand your module to work with several distributions, it is possible to use the 'case' construction is more conveniently, for example:

https://github.com/saz/puppet-memcached/blob/master/manifests/params.pp#L4
https://github.com/puppetlabs/puppetlabs-postgresql/blob/master/manifests/params.pp#L28

However, in my patch I inherit = $::osfamily ? { to stick with style.

olevole added 3 commits October 14, 2018 06:36
changes for FreeBSD are trivial and mainly relate to
an alternative path to configuration and executable files.
So, the standard way for 3rd-party config files in FreeBSD:
  /usr/local/etc{/rsnapshot}
and for binaries:
  /usr/local
Also, define @cmd_rsnapshot in cron.erb via config_cmd_rsnapshot
changes for FreeBSD are trivial and mainly relate to
an alternative path to configuration and executable files.
So, the standard way for 3rd-party config files in FreeBSD:
  /usr/local/etc{/rsnapshot}
and for binaries:
  /usr/local
Also, define @cmd_rsnapshot in cron.erb via config_cmd_rsnapshot
@loomsen
Copy link
Owner

loomsen commented Oct 20, 2018

Hi Oleg,

thank you for your work! I will gladly accept your PR once we manage to get the travis checks passing. I think it should suffice to set the puppet gem version in .travis.yml to something < 5.0? I'm not actively using puppet anymore, could you please check that?

Thank you!

@loomsen
Copy link
Owner

loomsen commented Oct 20, 2018

Actually, it looks like we should rather bump the rvm version in .travis.yml.

@loomsen
Copy link
Owner

loomsen commented Oct 20, 2018

I created a PR on your master with the according fixes.
olevole#1

@loomsen
Copy link
Owner

loomsen commented Oct 20, 2018

Hi Oleg, thanks for merging the changes. So, the installation problem seems to be solved, however, the builds still fail. Not sure why though.

This is the last successful build, where I just changed what you merged

Your changes seem to break something, but I can't figure out why. Maybe you can look into this?
Also, could you please add FreeBSD to supported operating systems in metadata.json, please?

@olevole
Copy link
Author

olevole commented Oct 20, 2018

Yes, it looks strange to me also. I will try to look at it in the next week. Thanks a lot for your help/tips.
Not sure if adding to metadata.json can fix the problem. A very large number of modules have unofficial FreeBSD support but due to the fact that the authors of the modules do not use FreeBSD they are afraid to add it into supported OS ;-) I'll take a little timeout to solve this problem.

@@ -190,19 +190,21 @@
# create cron files for each backup level
# merge possible cron definitions to one
$real_cron = deep_merge($rsnapshot::params::cron, $rsnapshot::cron, $hash[cron])
$cmd_rsnapshot = pick($rsnapshot::cmd_rsnapshot, $rsnapshot::params::config_cmd_rsnapshot)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't find $rsnapshot::cmd_rsnapshot (no $cmd_rsnapshot in init.pp). Seems to produce warnings in the test suite.

@smortex
Copy link

smortex commented Oct 21, 2018

I'm not actively using puppet anymore, could you please check that?

@loomsen For the record, if you are not using Puppet anymore and maintaing this module is low priority for you, you may consider migrating the project to voxpupuli.

I guess that beyond this pull request, more changes would be appreciable by the community (e.g. switching from params.pp to Hiera; switching from erb to epp templates; etc).

I am not using rsnapshot and reached this PR via private mail from @olevole, but would be pleased to help if some guidance is needed.

@loomsen
Copy link
Owner

loomsen commented Oct 31, 2018

I am not using rsnapshot and reached this PR via private mail from @olevole, but would be pleased to help if some guidance is needed.

Hi @smortex , I'd be pleased to migrate this project to voxpupuli. Would be cool to get in touch with you, can you write me an email? loomsen at gmail.

Thank you :)

@smortex
Copy link

smortex commented Nov 1, 2018

@loomsen I am moving and will not be able to actively assist in the next weeks. I pinged the #voxpupuli people on IRC and linked to this issue.

@alexjfisher
Copy link

@loomsen I've sent you a github invitation. After you accept, you should be able to transfer repository ownership to VP.

Any questions, could you drop by on IRC or slack?

Many thanks,
Alex

@loomsen
Copy link
Owner

loomsen commented Nov 1, 2018

@loomsen I've sent you a github invitation. After you accept, you should be able to transfer repository ownership to VP.

Thank you @alexjfisher, I'm pretty busy atm, but I will try and find some time over the weekend. I'll text you guys up on IRC then.

Regards
Norbert

@loomsen
Copy link
Owner

loomsen commented May 26, 2020

@olevole @alexjfisher Sorry for the "late" reply, life kind of got in my way. I'm totally out of puppet development, and would be more than happy to migrate this module now. If any of you guys are still around and willing to help, ping me please.

@alexjfisher
Copy link

@olevole @alexjfisher Sorry for the "late" reply, life kind of got in my way. I'm totally out of puppet development, and would be more than happy to migrate this module now. If any of you guys are still around and willing to help, ping me please.

@loomsen Sure. But see my comment #16 (comment) At the moment, very few of our modules use the PDK and those that do are in a bit of a limbo state whilst we figure out what the release workflow should look like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants