[Pkg-giraffe-discuss] z-push vs z-push-common
Carsten Schoenert
c.schoenert at t-online.de
Wed Jan 4 20:24:49 UTC 2017
Hello Roel,
Am 03.01.2017 um 15:31 schrieb Roel van Meer:
> first of all, happy new year everyone. May you survive 2017 in good health!
thanks, wish you too a happy new year!
> Currently, the z-push packaging creates a z-push package and a z-push-common
> package. The z-push package is a metapackage without any files. I was
> wondering if there is a good reason to keep it this way?
>
> If z-push is an empty package anyway, I would prefer moving everything from
> z-push-common into z-push and drop the z-push-common package, but perhaps
> there are good reasons to keep it this way that I'm not aware of?
This depends if there are things that only need files from
z-push-common, for example if a webserver don't need other packages to
get work. OTOH there are still a lot of packages and the number should
be decreased much as possible ...
Currently I would think much about this, if it's easier for you to get
recent z-push version running than just do it. If we will come together
and think about a upload into NEW we will look into every package again
and will make a final decision then.
I can't say much about a "correct" package structure as I'm not that
deep into the interns of z-push anymore.
--
Regards
Carsten Schoenert
More information about the Pkg-giraffe-discuss
mailing list