- split functionality that needs prj/pac as commandline arguments into a seperate tool (oscremote) - implement 'info' command - implement 'mv' command - creation of new project (workaround: editmeta ) - creation of new package (workaround: editmeta prj ) - editing of user data - editmeta: validate input - updatepacmetafromspec -- is that useful? In which form would this be integrated best? -> it doesn't cope with subpackages as well as I initially thought checkin: - handle error if PUT fails, so the change is not committed to localmeta results: aggregate results of all packages in a project -> packstatus: http://api.opensuse.org/result/KDE:KDE3/packstatus http://api.opensuse.org/result/KDE:KDE3/packstatus?summary http://api.opensuse.org/result/KDE:KDE3/packstatus?summaryonly implement a package search / indexing > BTW: Can I upload a src.rpm instead of a tarball also? no, because not all tools will be able to handle a src.rpm. And you will not be able to build non rpm packages from it. But someone could patch the commandline tool osc to import a src.rpm by extracting it (hint hint ;) 17:24 und wie waere ein osc link src_project src_package [local_package] ?:p or: "linkpac"? just create a _link file with the content ich hab nen vorschlag fuer osc sagen wir ich leg ein server:mail/foo123 an dann waere es cool sowas zu koennen wie osc importfromspec server:mail foo123 bug: % osc rm subversion.de.po.bz2 subversion.nb.po.bz2 D subversion.de.po.bz2 D subversion.nb.po.bz2 poeml@aust ~/pac/opensuse/Subversion/subversion % osc ci subversion.de.po.bz2 subversion.nb.po.bz2 Sending subversion.changes Deleting subversion.de.po.bz2 Deleting subversion.nb.po.bz2 Sending subversion.viewcvs.conf Transmitting file data ..