flatpak-builder icon indicating copy to clipboard operation
flatpak-builder copied to clipboard

Tool to build flatpaks from source

Results 197 flatpak-builder issues
Sort by recently updated
recently updated
newest added

_From @ace13 on May 3, 2017 12:38_ Currently, flatpak-builder seems to assume - in most cases rightfully so - that any build of an extension is for a runtime. Was...

## Flatpak-builder version flatpak-builder 1.0.10 ## Description of the problem Feature Request: allow patches/.diff files to be fetched via internet.

### Checklist - [X] I agree to follow the [Code of Conduct](https://github.com/flatpak/flatpak/blob/master/CODE_OF_CONDUCT.md) that this project adheres to. - [X] I have searched the [issue tracker](https://www.github.com/flatpak/flatpak-builder/issues) for a feature request that...

**TL;DR:** There are two ideas I have to make using flatpak-builder easier for both IDEs and command-line tools. Right now, if I modify a module in a Flatpak, the entire...

### Checklist - [X] I agree to follow the [Code of Conduct](https://github.com/flatpak/flatpak/blob/master/CODE_OF_CONDUCT.md) that this project adheres to. - [X] I have searched the [issue tracker](https://www.github.com/flatpak/flatpak-builder/issues) for a bug that matches...

## Linux distribution and version GNU Guix System 1.2.0 ## Flatpak-builder version 1.0.11 (flatpak install) ## Flatpak version 1.10.2 ## Description of the problem I don't know if this is...

## Description of the problem I have a question regarding the `env` field of the `build-options`. The doc for flatpak-manifest states that this is a dictionary (object) of env values....

### Checklist - [X] I agree to follow the [Code of Conduct](https://github.com/flatpak/flatpak/blob/master/CODE_OF_CONDUCT.md) that this project adheres to. - [X] I have searched the [issue tracker](https://www.github.com/flatpak/flatpak-builder/issues) for a bug that matches...

## Flatpak-builder version `flatpak-builder 1.0.1` ## Description of the problem The correct place for those files _is_ `metainfo`, see flatpak/flatpak#30, but `flatpak-builder` moves them to `appdata`, leaving `metainfo` empty.

Consider adding ability to specify custom autogen command for autotools sources. Use-case: today I wanted to build autotools projects that do not distribute generated autotools build files in the release...