how to manage software sources with CFEngine3?

316 views
Skip to first unread message

Kyle Schrama

unread,
Jan 9, 2013, 5:21:10 PM1/9/13
to help-c...@googlegroups.com
I'm currently using cfengine to manage the installed packages on ubuntu, but there's a package that i need to install from a PPA rather than from the standard ubuntu repos.  Is there a "right" way to do this in CFEngine, or should i just be hacking together some promises on apt-key and the source.list file?

Diego Zamboni

unread,
Jan 9, 2013, 5:29:41 PM1/9/13
to Kyle Schrama, Diego Zamboni, help-c...@googlegroups.com
There are no built-in mechanisms for specifying or adding repositories, but it should be as simple as promising contents for a file under /etc/apt/sources.list.d/, or a line in /etc/apt/sources.list.


--Diego


On Jan 9, 2013, at 4:21 PM, Kyle Schrama <nota...@gmail.com> wrote:

I'm currently using cfengine to manage the installed packages on ubuntu, but there's a package that i need to install from a PPA rather than from the standard ubuntu repos.  Is there a "right" way to do this in CFEngine, or should i just be hacking together some promises on apt-key and the source.list file?

--
You received this message because you are subscribed to the Google Groups "help-cfengine" group.
To post to this group, send email to help-c...@googlegroups.com.
To unsubscribe from this group, send email to help-cfengin...@googlegroups.com.
Visit this group at http://groups.google.com/group/help-cfengine?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Nick Anderson

unread,
Jan 9, 2013, 5:30:13 PM1/9/13
to help-c...@googlegroups.com
I think there is a sketch for that.

Repository::apt::Maintain Manage deb repositories in
/etc/apt/sources.list.d/ files or /etc/apt/sources.list

Brian Bennett

unread,
Jan 9, 2013, 5:37:17 PM1/9/13
to Diego Zamboni, Kyle Schrama, Diego Zamboni, help-c...@googlegroups.com
I managed a large environment (~500 systems) and we managed apt repositories with files promises. It could also be easily done with edit_line promises. So from a real world production environment, this works well.

After a copy or update set a class that will trigger an apt-get update.

For the apt keys, I would copy the key to a specific location then set a class that would trigger apt-key add. An alternative would be to copy the entire apt keyring (it's just an ordinary gnupg keyring), although I don't recommend that.

-- 
Brian

Kyle Schrama

unread,
Jan 18, 2013, 7:10:42 PM1/18/13
to help-c...@googlegroups.com
thanks for the help guys.  It's good to know i'm on the right track.
Reply all
Reply to author
Forward
0 new messages