formulas-devel February 2013

formulas-devel@lists.stg.fedorahosted.org

7 participants
2 discussions

next steps...
by Kevin Fenzi 25 Mar '13

25 Mar '13

alright then. ;) So, what things do we need: - rules (somewhat discussed), need to see if we need any more. - frontend design / coding. Any GUI designers around? or does anyone know any that would be interested in working on this? - backend design / coding. We may be able to piggyback here on a 'application store' type thing. I'm not sure if/when that might exist. Anyone interested in working on this? - Some simple formulas we can test without frontend/backend. Herlo made one, I need to poke at it some, but others would be welcome. I think we are going to need a library of things available for reuse in formulas and to figure out structure. Also, are there any common use cases we should try and cover in the first few example formulas? - Can we build in some QA/testing/docs ? As we go, is there a way to build things so it's easier to test/document? I think one git repo per formula is likely. formulas versions would then be 'foo-YYYYMMDD-githash' or something. I'm going to try and work on a roadmap on the trac site with things we need before 1.0 of the formulas framework and we can see if we can find folks to work on those. kevin

7 21

Welcome and discussion starter
by Kevin Fenzi 16 Feb '13

16 Feb '13

Welcome everyone. I'm sure many of you have seen: https://fedoraproject.org/wiki/Fedora_formulas and http://lists.fedoraproject.org/pipermail/devel/2013-January/176011.html but if not, please do go scan through those. I'd like to start discussion here on a number of things we should decide and figure out and design before we start digging into too many implementation details. I'd like to suggest we work on the assumption that a formula is a signed tag/commits in a git repo. I think making formulas rpms is going to be too much overhead for us. I think it might be best to look at rules/guidelines we want to have first, keeping them as high level above implementation details as we can at this point. I'll start with a stawman for people to add to/pick apart: * Must use packages from the package collection, installed with the normal distro tools. * Must not change non config files in those packages. ie, only can change files marked config in the package management system or add new files. * Can depend on other formulas having been applied. * Can conflict with other formulas. ("Sorry, you have apache server formula installed, so lighthttpd cannot be run") * Must have an 'uninstall' method. (return config, remove packages) * May be interactive and ask users questions, but should also include a set of default answers that can be used with --nointeractive. * Must log when they were run / possibly output. * Must have a detailed use case/description. * Your idea here. Thoughts? kevin

7 17

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

formulas-devel February 2013