jheiss
commented
12 years ago This requires clients to be somewhat more aware of the Rails server than they are currently. Tpkg clients currently have (optionally) some knowledge of the Rails server via the report_server setting in tpkg.conf. However, that's set to a specific URL for the reporting API. We should probably make that tpkg.conf setting more generic such that the client is configured with the top level URL for the Rails server as a whole, and then constructs the reporting and upload URLs based off that top level URL.
Was: https://sourceforge.net/apps/trac/tpkg/ticket/5#comment:1
From Jim Yanko:
Would like to see tpkg provide an option to just upload a tpkg binary to the repository.
tpkg —upload eds-5.22.5-5.tpkg # something like this would be nice
We already have a --download option, and there is a side script which performs upload, but it is not integrated to the main tpkg tool.
The script that is used for uploading is.
tpkg_uploader.rb -f $HOME/TPKGBUILD/scratch/eds_config_qa-2.10.0-16/eds_config_qa-2.10.0-16.tpkg
Which is currently installed by another tpkg tpkg_uploader-1.5-4.tpkg itself
$ tpkg --qf /Users/jyanko/tpkg_test/home/t/bin/tpkg_uploader.rb /Users/jyanko/tpkg_test/home/t/bin/tpkg_uploader.rb: tpkg_uploader-1.5-4.tpkg
Since tpkg is used to create new packages, it would be nice for it to provide a little cleaner way to upload packages to the repo after they're created.
Was: https://sourceforge.net/apps/trac/tpkg/ticket/5