[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Current status of your swt-gtk package



On Wed, Oct 05, 2005 at 01:03:33PM -0500, Billy Biggs wrote:
> Shaun Jackman (sjackman@gmail.com):
> 
> > > as we spoke some time ago you wanted to get your swt-gtk packages to
> > > testing and then supersede them by the ones generate from the new
> > > Eclispe 3.1 (3.1.1 in the meanwhile). My packages are ready and
> > > gracefully work as a replacement to your packages. While doing this
> > > work I checked your package and saw that it violates the Debian Java
> > > Policy in more then one way. Sure, the things are easy to fix. I
> > > just wonder if you or we should put work into this and then throw it
> > > away later.
> > >
> > > At DevJam meeting I spoke with several people about the situation.
> > > They all think we should replace the existing swt-gtk package as
> > > soon as possible to give it enough time to stabilize and get testing
> > > through a big userbase before the next release of Debian. Whenever
> > > that will happen.
> > >
> > > What's your opinion about this now?
> > 
> > Billy Biggs, an SWT developer, is working on producing a separate SWT
> > source package.
> 
>   Shaun and Michael,
> 
>   I'm sort of torn on this issue myself though.
> 
>   - In my opinion, SWT should have a source download that is more easily
>     buildable, and so I'm working on this.
> 
>     However, the Eclipse srcIncluded zip is maybe better for this as it
>     is now.
> 
>   - The SWT plug-in is different in its filesystem layout in the
>     Eclipse plugins folder than the standalone SWT.
> 
>     However, the source code is clearly the same, and it is easy to
>     create SWT source packages since its only the final filesystem
>     layout that differs.
> 
>   So regardless of what you guys want to do, know that I don't really
> have a strong opinion on the matter.  I think if it were up to me, I'd
> just go with Michael's packages since I think it will be easier to
> coordinate fixing bugs.

I dont know what to do. My opinion would be to build all from the
eclipse source to make sure both eclipse and swt have the same versions.
Eclipse is a critical application. We need to make sure it works. It
would not be too difficult to produce both layouts from one source like
eclipse.


Until we have a real solution I will do a (sponsored) upload of Eclipse
3.1.1-1 to the Debian archive to get more feedback and be able to use the
Debian BTS for bug/wishlist/patch tracking. This eclipse will contain
its own SWT packages which just Conflicts with Shauns. No Replaces. Both
will reside in the archive. They can just not get installed both at the
same time. We (my sponsor and I) will upload Eclipse to the contrib section
for now as it depends on lucene and tomcat5 which are still in contrib.
When both have moved to then main section we will move Eclipse to the main
section too. No showstopper then anymore.


Cheers,
Michael
-- 
Escape the Java Trap with GNU Classpath!
http://www.gnu.org/philosophy/java-trap.html

Join the community at http://planet.classpath.org/



Reply to: