importing XML, CSS, Upload, Xdebug, Execute Script, Execute Browser etc. pp. plugins into Quanta
Andreas Pakulat
apaku at gmx.de
Mon Jun 7 16:27:59 UTC 2010
- Previous message: importing XML, CSS, Upload, Xdebug, Execute Script, Execute Browser etc. pp. plugins into Quanta
- Next message: importing XML, CSS, Upload, Xdebug, Execute Script, Execute Browser etc. pp. plugins into Quanta
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On 07.06.10 18:40:41, Alexander Shaduri wrote:
> On Mon, 7 Jun 2010 16:13:50 +0200
> Milian Wolff <mail at milianw.de> wrote:
> > > Thank you both for your answers.
> > > Just one quick question though: Would these plugins be distributed
> > > as part of Quanta, or separately? That is, would I have to have Quanta
> > > installed to use them in KDevelop?
> >
> > That completely depens on your distributor. They are free to create separate
> > packages for each plugin and use dependencies to install them when the user
> > wants "Quanta" or "KDevelop".
> >
> > This is out of our reach.
> >
> > Note: I'd like distributors to do that, as long as they do it correct ;-)
>
> Well, that mostly depends on how you release the tarballs.
No it doesn't. Look at kdebase or other kde modules shipping multiple
apps/libs. Distributors will split those "big" tarballs into separate
packages if they find that their users want to install only one app from
the bunch.
> If you release the plugins as separate tarball(s), the distributor
> is likely to follow the same pattern.
>
> For me, the most logical way of packaging them (including making
> the tarballs) would be something like:
> * kdevplatform (no plugins);
> * kdevelop (contains only plugins that are unusable outside of it);
> * quanta (contains only plugins that are unusable outside of it);
> * kdevplatform-plugins-base (the most common plugins for both);
> * kdevplatform-plugins-webdev (xml, css, ...);
> * (possibly) kdevplatform-plugins-php (unless it's included in webdev).
> etc...
This doesn't make the slightest sense. We want to release a complete app as
single package as much as possible. Hence there's a KDevelop package, a
Quanta package and a KDevPlatform package as it makes sense to split out
the common libs/plugins. Users that do use our source packages don't want
to go hunting for n packages if they want 1 app.
Andreas
--
Your mode of life will be changed for the better because of new developments.
- Previous message: importing XML, CSS, Upload, Xdebug, Execute Script, Execute Browser etc. pp. plugins into Quanta
- Next message: importing XML, CSS, Upload, Xdebug, Execute Script, Execute Browser etc. pp. plugins into Quanta
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the KDevelop-devel
mailing list