On Wed, 13 Mar 2002 19:13:44 +0100 Max Horn <[EMAIL PROTECTED]> wrote:
> >So, package name `fooN' will become glib2-0, where foo=glib2, N=0 > >and hyphen is for distinguish N=0 with N=20. [...] > > Do you want to say, you do this to be prepared for glib 20.0 ? Yes. > I mean, what is bad about the package name glib2? Assuming there will > be a version 2.2, it will be glib2-2.2 > > If say 2.4 was binary incompatible, we could make a glib24-2.4 > package, however, I strongly doubt that will be necessary - for a > binary compatibility break, they'll go to version 3 I think. According to our shlibs policy, package name should contains it's major version number. It is 0 for glib2 libraries. Probably, gtk peoples will keep compatibility under glib2 and will changes it's name to glib3 if compatiblility breaks. But should we break our policy and make a special naming rule for glib? -- Masanori Sekino mailto:[EMAIL PROTECTED] http://hp.vector.co.jp/authors/VA008857/ _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
