Moving pangomm into its own tarball

View: New views
5 Messages — Rating Filter:   Alert me  

Moving pangomm into its own tarball

by Murray Cumming :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'm thinking of moving pangomm out of gtkmm and into its own tarball,
keeping all the same shared library names and installed include
directories. This would allow cluttermm to depend on pangomm without
depending on all of gtkmm even at build time.

I wonder if this would be bad for anyone. The ABI would not change, and
sane distros already package pangomm separately.

--
murrayc@...
www.murrayc.com
www.openismus.com

_______________________________________________
gtkmm-list mailing list
gtkmm-list@...
http://mail.gnome.org/mailman/listinfo/gtkmm-list

Re: Moving pangomm into its own tarball

by Jonathon Jongsma-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Murray Cumming wrote:
> I'm thinking of moving pangomm out of gtkmm and into its own tarball,
> keeping all the same shared library names and installed include
> directories. This would allow cluttermm to depend on pangomm without
> depending on all of gtkmm even at build time.
>
> I wonder if this would be bad for anyone. The ABI would not change, and
> sane distros already package pangomm separately.
>
>  
would this mean splitting it into a separate svn repository too, or not?
_______________________________________________
gtkmm-list mailing list
gtkmm-list@...
http://mail.gnome.org/mailman/listinfo/gtkmm-list

Re: Moving pangomm into its own tarball

by Murray Cumming :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Mon, 2008-07-14 at 09:28 -0500, Jonathon Jongsma wrote:

> Murray Cumming wrote:
> > I'm thinking of moving pangomm out of gtkmm and into its own tarball,
> > keeping all the same shared library names and installed include
> > directories. This would allow cluttermm to depend on pangomm without
> > depending on all of gtkmm even at build time.
> >
> > I wonder if this would be bad for anyone. The ABI would not change, and
> > sane distros already package pangomm separately.
> >
> >  
> would this mean splitting it into a separate svn repository too, or not?

Yes, that would be sensible.

--
murrayc@...
www.murrayc.com
www.openismus.com

_______________________________________________
gtkmm-list mailing list
gtkmm-list@...
http://mail.gnome.org/mailman/listinfo/gtkmm-list

Re: Moving pangomm into its own tarball

by Jonathon Jongsma-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Murray Cumming wrote:

> On Mon, 2008-07-14 at 09:28 -0500, Jonathon Jongsma wrote:
>  
>> Murray Cumming wrote:
>>    
>>> I'm thinking of moving pangomm out of gtkmm and into its own tarball,
>>> keeping all the same shared library names and installed include
>>> directories. This would allow cluttermm to depend on pangomm without
>>> depending on all of gtkmm even at build time.
>>>
>>> I wonder if this would be bad for anyone. The ABI would not change, and
>>> sane distros already package pangomm separately.
>>>
>>>  
>>>      
>> would this mean splitting it into a separate svn repository too, or not?
>>    
>
> Yes, that would be sensible.
>  
Yes, it seems sensible to me as well.  But it also seems like it could
be a bit painful to extract unless the plan is to just drop all previous
history and 'svn rm' it from the old repository and 'svn add' it to the
new one (which I personally think is a bad idea).  Maybe the GNOME
sysadmins can do svn surgery somehow.

Jonner
_______________________________________________
gtkmm-list mailing list
gtkmm-list@...
http://mail.gnome.org/mailman/listinfo/gtkmm-list

Re: Moving pangomm into its own tarball

by Murray Cumming :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Mon, 2008-07-14 at 10:30 -0500, Jonathon Jongsma wrote:      

> >> would this mean splitting it into a separate svn repository too, or not?
> >>    
> >
> > Yes, that would be sensible.
> >  
> Yes, it seems sensible to me as well.  But it also seems like it could
> be a bit painful to extract unless the plan is to just drop all previous
> history and 'svn rm' it from the old repository and 'svn add' it to the
> new one (which I personally think is a bad idea).  Maybe the GNOME
> sysadmins can do svn surgery somehow.

I guess it would be enough to start the new pangomm module as a copy of
gtkmm and then remove the part we don't want.

But GNOME sysadmin help is currently hard to find (though not as bad as
it once was), so I might be forced to just drop the history.

--
murrayc@...
www.murrayc.com
www.openismus.com

_______________________________________________
gtkmm-list mailing list
gtkmm-list@...
http://mail.gnome.org/mailman/listinfo/gtkmm-list
LightInTheBox - Buy quality products at wholesale price