On Tue 12 Nov 2013 04:12:41 PM CET, Marco Martin wrote:
an update on the direction i'm going.
At this point using invocation of the external tool osc it can fetch both the
proper rpm filesize and correct rpm name, buiold number included.
One problem is that right now it's based on the extension of the uploaded file
being ".desc", but apart being hacky, the branch mart/obsmanager of the server
works.
one idea was, instead of requiring a file to be uploaded is to have some data
source concept..
The database already has the concept of "externpath", so, if the user while
creating an asset from obs does instead specify a repo and a package (like
home:foo) the externpath becomes
obs://build.merproject.org/home:foo/packagename
when this happens a desc file gets created (that should probably become json,
to ensure a bit of expandibility) and it works as now in the mart/obsmanager
branch
when the publisher approves a pending request, another external osc invokation
happens automatically and it does a copypac of the package between home:foo
and kde:stable:apps, so the approval procedure would be completely web based
not sure if i explained myself clearly at all.. but, comments? ;)
The idea of submitting just a repository path and a package name is
something I was expecting from the beginning. But you need some online
validation mechanism in order to make sure that the user fills
correctly these fields.
_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
