[opensuse-packaging] -mini packages purpose
Hi: What is the specific reason for having foobar-mini packages ? I guess those provides less functionality but for what use cases are needed or what is the rationale behind them ? -- "If eval() is the answer, you're almost certainly asking the wrong question." --Rasmus Lerdorf Cristian Rodríguez R, Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Cristian Rodriguez wrote:
What is the specific reason for having foobar-mini packages ?
I guess those provides less functionality but for what use cases are needed or what is the rationale behind them ?
To minimize build dependencies and/or break cycles. They only live inside autobuild, because they have no use in a running system. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hello, On Nov 9 10:22 Michal Marek wrote:
Cristian Rodriguez wrote:
What is the specific reason for having foobar-mini packages ?
I guess those provides less functionality but for what use cases are needed or what is the rationale behind them ?
To minimize build dependencies and/or break cycles. They only live inside autobuild, because they have no use in a running system.
In the Java/JPackage world we use *-bootstrap as package name for such kind of packages, e.g.: antlr-bootstrap.rpm, ecj-bootstrap.rpm, xerces-j2-bootstrap.rpm, xml-commons-apis-bootstrap.rpm, xml-commons-resolver-bootstrap.rpm, xml-commons-which-bootstrap.rpm Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Michal Marek wrote:
Cristian Rodriguez wrote:
What is the specific reason for having foobar-mini packages ?
I guess those provides less functionality but for what use cases are needed or what is the rationale behind them ?
To minimize build dependencies and/or break cycles. They only live inside autobuild, because they have no use in a running system.
OK, so what is rpmlint-mini doing in http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/ in that case? Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Freitag 09 November 2007 schrieb Wolfgang Rosenauer:
Michal Marek wrote:
Cristian Rodriguez wrote:
What is the specific reason for having foobar-mini packages ?
I guess those provides less functionality but for what use cases are needed or what is the rationale behind them ?
To minimize build dependencies and/or break cycles. They only live inside autobuild, because they have no use in a running system.
OK, so what is rpmlint-mini doing in http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/ in that case?
Providing a rpmlint with minimal dependencies to "minimize build dependencies". I hope you're not protesting that we upload packages only interesting inside autobuild to the public. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Stephan Kulow wrote:
Am Freitag 09 November 2007 schrieb Wolfgang Rosenauer:
Michal Marek wrote:
Cristian Rodriguez wrote:
What is the specific reason for having foobar-mini packages ?
I guess those provides less functionality but for what use cases are needed or what is the rationale behind them ? To minimize build dependencies and/or break cycles. They only live inside autobuild, because they have no use in a running system. OK, so what is rpmlint-mini doing in http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/ in that case?
Providing a rpmlint with minimal dependencies to "minimize build dependencies". I hope you're not protesting that we upload packages only interesting inside autobuild to the public.
Absolutely not ;-) I was just mentioning that they obviously not only live in autobuild and I wondered if it was intentionally or not but even better if it is. Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Friday 09 November 2007, Wolfgang Rosenauer wrote:
Absolutely not ;-) I was just mentioning that they obviously not only live in autobuild and I wondered if it was intentionally or not but even better if it is.
The long term plan is to add rpmlint checking to autobuild. see bug 297050 Greetings, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Friday 09 November 2007, Dirk Mueller wrote:
The long term plan is to add rpmlint checking to autobuild. see bug 297050
s,autobuild,buildservice, Sorry for the confusion, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (6)
-
Cristian Rodriguez -
Dirk Mueller -
Johannes Meixner -
Michal Marek -
Stephan Kulow -
Wolfgang Rosenauer