[opensuse-buildservice] Ignoring files in a osc checkout
Hi, I wonder if there's any way to have some files ignored by osc in a directory that is a project or package checkout. Example: $ osc co GNOME:Factory libwnck [...] $ cd GNOME:Factory/libwnck $ touch ignore-this $ osc status ? ignore-this And I don't want to have ignore-this here. It's not that much about appearing in 'osc status' than the fact that I don't want this file to be commitable. There's a hack which works with osc. If I create a plugin and do: exclude_stuff.append('ignore-this') then the file will be ignored. However, this will only work with clients that are using the osc python modules, and therefore it's not a perfect solution. So, back to my question :-) Is there some local metadata that can be set for this? If no at the moment, is this something that would be desirable? Vincent -- Les gens heureux ne sont pas pressés. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Sun, Sep 21, 2008 at 05:29:07AM +0200, Vincent Untz wrote:
Hi,
I wonder if there's any way to have some files ignored by osc in a directory that is a project or package checkout.
Example: $ osc co GNOME:Factory libwnck [...] $ cd GNOME:Factory/libwnck $ touch ignore-this $ osc status ? ignore-this
And I don't want to have ignore-this here. It's not that much about appearing in 'osc status' than the fact that I don't want this file to be commitable.
There's a hack which works with osc. If I create a plugin and do: exclude_stuff.append('ignore-this') then the file will be ignored.
However, this will only work with clients that are using the osc python modules, and therefore it's not a perfect solution.
So, back to my question :-) Is there some local metadata that can be set for this? If no at the moment, is this something that would be desirable?
Vincent
Both a way to configure additional ignores via .oscrc, and a way to do this via (local?) metadata per package would seem to be desirable to me. Both don't exist at the moment. I'm not sure if only one of them or both should be implemented. Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development
participants (2)
-
Peter Poeml
-
Vincent Untz