* Marc Kleine-Budde <[email protected]> schrieb: > Hey Enrico, > > please don't drop the mailinglist from CC!
okay, posting directly to the list (w/o cc) > > uhm, that's bad. requires the import system to know all these > > directories before patching. naturally it knows some canonical > > package name and works upon the an git tree coming from the > > upstream's vcs, which of course does not contain such an > > prefix directory (as found in tarballs). > > what about just taking the name of the tarball then and see > where it breaks. Might be a way. nevertheless i'll need some mapping. Maybe a generic mapping between a normalized and the individual vendor's namespaces. (hmm, that calls for prolog or lisp ;-)). > > I doubt that will help me in importing ptxdist patches ontop > > upstream release tags ;-o > > You asked about handling of patch updates :P My concern is how to handle cases where ptxdist's patches get updated. In this case I need to import them to a new refname. BTW: I'm also looking for a way to handle queues of new releases (for further inspection) directly within git, thinking about using an own ref namespace for that ... unfortunately git doesnt seem to provide a tool to manipulate arbitrary refs yet ;-o cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: [email protected] mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ---------------------------------------------------------------------- -- ptxdist mailing list [email protected]
