Allow uploading data for single (rather than all) packages (in build server context)?

[hartwork]

Hi!

I have a build server that builds ebuilds as they appear in Gentoo. I consider integrating an upload to portagefilelist.de but it seems wasteful to upload data for all packages after every single build. If that kind of data is of interest to have to you, it would be great to have a mode to collect data for just one single package. What do you think?

Best, Sebastian

[tuxmainy]

Hi,
PFL should only upload builds which are newer than "last run"-timestamp. This is the primary idea behind /var/lib/pfl/pfl.info or $HOME/.pfl.info . So as long as you do not remove this file between the builds PFL should only upload diffs?!

regards
Daniel

[hartwork]

Hi @tuxmainy, in my environment — context is https://github.com/hartwork/binary-gentoo — there is no info from a previous run because every build starts from the same state docker image so it would always be the first run.

[tuxmainy]

So adding an argument to the pfl call like 'pfl net-misc/bridge-utils-1.6' would be an option? That way one must use CPV and not CP.

[hartwork]

That would totally work for me, I guess, yes!

[hartwork]

@tuxmainy any news?

[bananas-repos]

Dusting old issues here.

After I get the hang of the e-file I will look into it.

[bananas-repos]

@hartwork In the upcomming release, there will be a option to provide a package atom. It will only collect the data of the provided package and upload it.

[hartwork]

@bananas-repos cool!

[bananas-repos]

Build a release. Will take some time to be in the portage tree.