https://bugzilla.novell.com/show_bug.cgi?id=212565#c2 Peter Poeml changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mls@novell.com, suse-tux@gmx.de Status|NEW |ASSIGNED --- Comment #2 from Peter Poeml 2007-07-13 04:28:26 MST --- quoting from recent discussion: [opensuse-buildservice] Minutes of build service meeting at SUSE 2007-07-06 (2) local build of linked packages Exhaustive list of _link file features: http://opensu.se/~darix/link.xml.txt Questions: - whether to handle this on the server or client side - whether _link file contents should be stored as XML metadata instead - whether _link contents (and patches) are "metadata" at all, or "source" the distinction is relevant with regard to triggering rebuilds. Generally, there are properties which may trigger a rebuild, and others which may not. Now, metadata changes do not trigger rebuilds, source changes do. Use cases: - linked package, local build, either a) the sources and patches need to be send to the server and the patched sources returned to the client for building, or b) or the the client needs to implement the same logic as the server, and possibly needs to check out all packages linked to and apply the patches - link to locally modified package (hardly possible to handle this on the server side) - link to other link (no problem for the server) - when trying to check in changed sources, but encountering a "not allowed", create a linked package on-the-fly and commit the local changes as linked package instead. a.k.a. "Adrian use case" ;-) Extension to this train of thought: Possibly submit a "merge request" Theoretically, a /source/prj/pac request should provide information about linked packages, where applicable (like: package and project linked to) AI for mls: see how well the code handling linked packages can be separated and placed in build.rpm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=212565 User suse-tux@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=212565#c4 --- Comment #4 from Marcus Hüwe 2008-02-10 13:01:41 MST --- I just hacked a small perl script which patches a linked package. The idea behind it is: - osc checks out the linked package + the source package (and puts all files into a temporary dir) - the script is called which applies all patches specified in the _link file - now build can be called by osc I just attached a tarball which contains two source files, psrc.pl (the script itself), BSPatch.pm (patchspec() and topaddspec() are just copied and pasted from bs_srcserver) and a test dir (simply run: perl psrc.pl --ldir test/ --spec test.spec to see how it works). I don't know if this script is useful or not but it might be a starting point... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=212565 User jw@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=212565#c6 --- Comment #6 from Juergen Weigert 2008-03-11 09:16:35 MST --- Created an attachment (id=200305) --> (https://bugzilla.novell.com/attachment.cgi?id=200305) perl hack to expand links, from within the suse network This is no solution for external users. It relies on direct connections to port 5352 of buildservice.suse.de It is quite old, sorry for not speaking up earlier. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.