|
View:
New views
13 Messages
—
Rating Filter:
Alert me
|
|
|
libslab plansHello control center people, and Owen (for Git expertise), and
Federico (as maintainer of gnome-main-menu) ! So gnome-control-center was one of the few unfortunate users of svn:externals, last month Owen investigated a good list of such users and noted this about gnome-control-center: |> gnome-control-center/trunk |> libslab http://svn.gnome.org/svn/gnome-main-menu/trunk/libslab/ |> |> I don't know the overall situation here. Is libslab used externally? |> If it needs to be kept like this, could be done as a git submodule; |> would need jhbuild support for submodules, since you have to |> git submodule update --init after cloning, and git submodule update |> after updating. (pretty simple) JHBuild supports git submodules (it is used by gstreamer), but afaik this solution would require that libslab be moved to its own repository. Cheers, Frederic _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansOn Wed, 2009-04-29 at 23:01 +0200, Frederic Peters wrote:
> Hello control center people, and Owen (for Git expertise), and > Federico (as maintainer of gnome-main-menu) ! > > So gnome-control-center was one of the few unfortunate users of > svn:externals, last month Owen investigated a good list of such > users and noted this about gnome-control-center: > > |> gnome-control-center/trunk > |> libslab http://svn.gnome.org/svn/gnome-main-menu/trunk/libslab/ > |> > |> I don't know the overall situation here. Is libslab used externally? > |> If it needs to be kept like this, could be done as a git submodule; > |> would need jhbuild support for submodules, since you have to > |> git submodule update --init after cloning, and git submodule update > |> after updating. (pretty simple) > > JHBuild supports git submodules (it is used by gstreamer), but afaik > this solution would require that libslab be moved to its own > repository. > dependency, rather than include it directly in g-c-c code. So CCing also Scott Reeves, gnome-main-menu maintainer -- Rodrigo Moya <rodrigo@...> _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansOn Thu, 2009-04-30 at 11:42 +0200, Rodrigo Moya wrote:
> On Wed, 2009-04-29 at 23:01 +0200, Frederic Peters wrote: > > Hello control center people, and Owen (for Git expertise), and > > Federico (as maintainer of gnome-main-menu) ! > > > > So gnome-control-center was one of the few unfortunate users of > > svn:externals, last month Owen investigated a good list of such > > users and noted this about gnome-control-center: > > > > |> gnome-control-center/trunk > > |> libslab http://svn.gnome.org/svn/gnome-main-menu/trunk/libslab/ > > |> > > |> I don't know the overall situation here. Is libslab used externally? > > |> If it needs to be kept like this, could be done as a git submodule; > > |> would need jhbuild support for submodules, since you have to > > |> git submodule update --init after cloning, and git submodule update > > |> after updating. (pretty simple) > > > > JHBuild supports git submodules (it is used by gstreamer), but afaik > > this solution would require that libslab be moved to its own > > repository. > > > hmm, I guess that would be the best solution, and use it as an external > dependency, rather than include it directly in g-c-c code. So CCing also > Scott Reeves, gnome-main-menu maintainer ugh, didn't CC Scott, now it is... -- Rodrigo Moya <rodrigo@...> _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansOn Thu, 2009-04-30 at 11:42 +0200, Rodrigo Moya wrote:
> On Wed, 2009-04-29 at 23:01 +0200, Frederic Peters wrote: > > JHBuild supports git submodules (it is used by gstreamer), but afaik > > this solution would require that libslab be moved to its own > > repository. > > > hmm, I guess that would be the best solution, and use it as an external > dependency, rather than include it directly in g-c-c code. So CCing also > Scott Reeves, gnome-main-menu maintainer We can move libslab to its own repository and make both g-c-c and gnome-main-menu use it as a submodule. I guess this will work: git filter-branch --subdirectory-filter libslab -- --all I'll test it in the morning. Federico _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansOn Thu, 2009-04-30 at 12:03 +0200, Rodrigo Moya wrote:
> On Thu, 2009-04-30 at 11:42 +0200, Rodrigo Moya wrote: > > On Wed, 2009-04-29 at 23:01 +0200, Frederic Peters wrote: > > > Hello control center people, and Owen (for Git expertise), and > > > Federico (as maintainer of gnome-main-menu) ! > > > > > > So gnome-control-center was one of the few unfortunate users of > > > svn:externals, last month Owen investigated a good list of such > > > users and noted this about gnome-control-center: > > > > > > |> gnome-control-center/trunk > > > |> libslab http://svn.gnome.org/svn/gnome-main-menu/trunk/libslab/ > > > |> > > > |> I don't know the overall situation here. Is libslab used externally? > > > |> If it needs to be kept like this, could be done as a git submodule; > > > |> would need jhbuild support for submodules, since you have to > > > |> git submodule update --init after cloning, and git submodule update > > > |> after updating. (pretty simple) > > > > > > JHBuild supports git submodules (it is used by gstreamer), but afaik > > > this solution would require that libslab be moved to its own > > > repository. > > > > > hmm, I guess that would be the best solution, and use it as an external > > dependency, rather than include it directly in g-c-c code. So CCing also > > Scott Reeves, gnome-main-menu maintainer > > ugh, didn't CC Scott, now it is... hmm, now I really am sure I added him, so something is removing it before it gets to the list... -- Rodrigo Moya <rodrigo@...> _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansOn Thu, 2009-04-30 at 05:35 -0500, Federico Mena Quintero wrote:
> We can move libslab to its own repository and make both g-c-c and > gnome-main-menu use it as a submodule. Uh... or we can make libslab a real library. Has the API changed very much lately? Is there anything that keeps it from being a standalone library? [I really want main-menu to be deprecated in favor of gnome-shell plus gnome-zeitgeist... if that happens and gnome-control-center ends up being the only user of libslab, well, I guess we could move the repository around again.] Federico _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansOn Thu, 2009-04-30 at 05:38 -0500, Federico Mena Quintero wrote:
> On Thu, 2009-04-30 at 05:35 -0500, Federico Mena Quintero wrote: > > > We can move libslab to its own repository and make both g-c-c and > > gnome-main-menu use it as a submodule. > > Uh... or we can make libslab a real library. Has the API changed very > much lately? Is there anything that keeps it from being a standalone > library? > from g-c-c point of view, it hasn't changed in a couple of years at least. And I think it hasn't changed that much from other points of view :-) > [I really want main-menu to be deprecated in favor of gnome-shell plus > gnome-zeitgeist... if that happens and gnome-control-center ends up > being the only user of libslab, well, I guess we could move the > repository around again.] > yeah -- Rodrigo Moya <rodrigo@...> _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plans>>> On 4/30/2009 at 5:28 AM, Rodrigo Moya <rodrigo@...> wrote:
> On Thu, 2009-04-30 at 05:38 -0500, Federico Mena Quintero wrote: >> On Thu, 2009-04-30 at 05:35 -0500, Federico Mena Quintero wrote: >> >> > We can move libslab to its own repository and make both g-c-c and >> > gnome-main-menu use it as a submodule. >> >> Uh... or we can make libslab a real library. Has the API changed very >> much lately? Is there anything that keeps it from being a standalone >> library? >> > from g-c-c point of view, it hasn't changed in a couple of years at > least. And I think it hasn't changed that much from other points of > view :-) The API is stable, but it's not an official blessed library. > >> [I really want main-menu to be deprecated in favor of gnome-shell plus >> gnome-zeitgeist... if that happens and gnome-control-center ends up >> being the only user of libslab, well, I guess we could move the >> repository around again.] >> > yeah There is also YaST that builds against libslab _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansOn Thu, 2009-04-30 at 16:52 -0600, Scott Reeves wrote:
> >>> On 4/30/2009 at 5:28 AM, Rodrigo Moya <rodrigo@...> wrote: > > On Thu, 2009-04-30 at 05:38 -0500, Federico Mena Quintero wrote: > >> On Thu, 2009-04-30 at 05:35 -0500, Federico Mena Quintero wrote: > >> > >> > We can move libslab to its own repository and make both g-c-c and > >> > gnome-main-menu use it as a submodule. > >> > >> Uh... or we can make libslab a real library. Has the API changed very > >> much lately? Is there anything that keeps it from being a standalone > >> library? > >> > > from g-c-c point of view, it hasn't changed in a couple of years at > > least. And I think it hasn't changed that much from other points of > > view :-) > > The API is stable, but it's not an official blessed library. > API change. -- Rodrigo Moya <rodrigo@...> _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansOn Mon, 2009-05-04 at 10:13 +0200, Rodrigo Moya wrote:
> I think the 1st thing we should do is remove the Bonobo dependency as > API change. Is that the app-shell-startup.[ch] stuff? In other news (AKA "Feddy gets off his ass"), I've started to massage libslab into a standalone library. I'll push it to a new "libslab" repository in a few minutes. I guess the best thing is to start branches in gnome-main-menu and gnome-control-center to use libslab as a standalone library. I'll do that once I have a libslab that builds. .. tap tap tap ... OK, I just created the libslab repository on git.gnome.org. There's a TODO file so that we can keep track of what's left to do to make it work :) Federico _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansOn Thu, 2009-05-07 at 20:16 -0500, Federico Mena Quintero wrote:
> On Mon, 2009-05-04 at 10:13 +0200, Rodrigo Moya wrote: > > I think the 1st thing we should do is remove the Bonobo dependency as > > API change. > > Is that the app-shell-startup.[ch] stuff? > > In other news (AKA "Feddy gets off his ass"), I've started to massage > libslab into a standalone library. I'll push it to a new "libslab" > repository in a few minutes. > > I guess the best thing is to start branches in gnome-main-menu and > gnome-control-center to use libslab as a standalone library. I'll do > that once I have a libslab that builds. > > .. tap tap tap ... > > OK, I just created the libslab repository on git.gnome.org. There's a > TODO file so that we can keep track of what's left to do to make it > work :) > dependency, since that would mean adding it as an external dependency to the GNOME release, right? Apart from that, if I've got time this weekend, I'll look at removing the Bonobo dependencies -- Rodrigo Moya <rodrigo@...> _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansLe vendredi 08 mai 2009, à 16:40 +0200, Rodrigo Moya a écrit :
> On Thu, 2009-05-07 at 20:16 -0500, Federico Mena Quintero wrote: > > OK, I just created the libslab repository on git.gnome.org. There's a > > TODO file so that we can keep track of what's left to do to make it > > work :) > > > from the TODO, not sure if g-c-c wants to use libslab as a external > dependency, since that would mean adding it as an external dependency to > the GNOME release, right? I would guess it shouldn't be much of a problem: the code was already used before. This is really just about splitting the code. Vincent -- Les gens heureux ne sont pas pressés. _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
|
|
Re: libslab plansLe mardi 12 mai 2009, à 02:11 +0200, Vincent Untz a écrit :
> Le vendredi 08 mai 2009, à 16:40 +0200, Rodrigo Moya a écrit : > > On Thu, 2009-05-07 at 20:16 -0500, Federico Mena Quintero wrote: > > > OK, I just created the libslab repository on git.gnome.org. There's a > > > TODO file so that we can keep track of what's left to do to make it > > > work :) > > > > > from the TODO, not sure if g-c-c wants to use libslab as a external > > dependency, since that would mean adding it as an external dependency to > > the GNOME release, right? > > I would guess it shouldn't be much of a problem: the code was already > used before. This is really just about splitting the code. I see that g-c-c has kept an internal copy of libslab, even though libslab has now been split in its own module. Do you guys intend to keep it this way? Note that I really don't think it's needed from a release management point of view. If yes, can you please apply the patch in http://bugzilla.gnome.org/show_bug.cgi?id=591138 Thanks, Vincent -- Les gens heureux ne sont pas pressés. _______________________________________________ gnomecc-list mailing list gnomecc-list@... http://mail.gnome.org/mailman/listinfo/gnomecc-list |
| Free embeddable forum powered by Nabble | Forum Help |