- implement 'info' command - implement 'mv' command - implement a live build log - creation of new project - creation of new package - editing of user data - editmeta: validate input - updatepacmetafromspec -- is that useful? In which form would this be integrated best? update: don't try to merge binary files 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 split functionality that needs prj/pac as commandline arguments into a seperate tool (oscremote) 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 16:20 < abauer> DuDE: