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 an FAQ section with answers to commonly asked questions about debian packaging #3

Open
pravi opened this issue Aug 23, 2020 · 2 comments
Assignees

Comments

@pravi
Copy link
Collaborator

pravi commented Aug 23, 2020

  1. What benefit does upstream get by supporting debian packaging workflow?

ohler55/oj#610 this can be quoted as a benefit to upstream when we run tests. When we run tests for native gems, we run them on many architectures and help fix bugs.

Another one is like we switch to newer ruby, rails etc before upstream does. So we test and report problems before they do it for many packages.

  1. Why do you want to run tests? Or why do you want to take github tarballs?

Tests help us during transitions (for example we want to update ruby or rails for all packaged gems in one go). We are happy to take rubygems.org as source if it contains tests.

  1. Why can't you take gems from from rubygems.org instead of creating debs?

celluloid/celluloid#263 (comment)

@bbatsov
Copy link
Contributor

bbatsov commented Aug 24, 2020

I think you should also expand on terminology like "upstream" and "downstream" as in:

This Packaging style guide outlines the recommended best practices for real-world programmers to write code that can be maintained both, upstream and downstream.

I'm relatively certain that the downstream part will confuse some people. :-)

@utkarsh2102
Copy link
Member

You're right! We'll indeed make this more explicit! :)

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

No branches or pull requests

3 participants