elvisangelaccio added a comment.

  In https://phabricator.kde.org/D7253#134703, @apol wrote:
  > In https://phabricator.kde.org/D7253#134653, @elvisangelaccio wrote:
  > > Main reason is having a simple way to run flatpak-builder with the proper 
arguments. Otherwise you have to copy-paste the command from somewhere (which 
could be error-prone).
  > >  One usually already has a build folder around, so the idea is you change 
some code, build it as usual and then you run this target to quickly test the 
change in flatpak.
  > Note that this is forcing that the file is in the root directory, this 
doesn't need to be necessarily the case. In fact xdg-portal-kde-test has it in 
a subdir.
  > This would already do what you're after:
  >  `alias fb=flatpak-builder --force-clean --ccache --require-changes 
--repo=repo app $@`
  > Such an alias/script could go in here: 
  > The reason why I'm discussing this is that I think one of the advantages of 
  Did you hit Submit too soon? :p  
  Anyway, an alias certainly works, I can live with that.

  R240 Extra CMake Modules


To: elvisangelaccio, apol, #frameworks
Cc: #frameworks, #build_system

Reply via email to