Pungi and anaconda interpret %packages differently
 

Hi,

I found out that pungi interprets %packages listed with a minus sign
(e.g. "-packagename") different from anaconda. Is this "by design"?

To be more precise:

When I specify a package in the kickstart file this way but other
packages in the list depend on it, the package is still installed
by anaconda (which is ok, I think). But pungi will always exclude
the package from the generated media, regardless the fact that
other packages depend on it.

It is not a big problem, I can just leave out all the minus-entries
in the pungi %packages list (it's not that much extra space), but a
consistent behavior would be nicer.

Any comments on this?

--
-- Jos Vos <jos@xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

Pungi and anaconda interpret %packages differently
 

On 08/03/2012 03:03 AM, Jos Vos wrote:

Hi,

I found out that pungi interprets %packages listed with a minus sign
(e.g. "-packagename") different from anaconda. Is this "by design"?

To be more precise:

When I specify a package in the kickstart file this way but other
packages in the list depend on it, the package is still installed
by anaconda (which is ok, I think). But pungi will always exclude
the package from the generated media, regardless the fact that
other packages depend on it.

It is not a big problem, I can just leave out all the minus-entries
in the pungi %packages list (it's not that much extra space), but a
consistent behavior would be nicer.

Any comments on this?



Another way that pungi differs is that it will do inclusive dep
resolution (grabs /every/ solver of a dep) vs an anaconda install which
will only grab the best solver of a dep.


That said, I think when I originally coded pungi, I wanted - to work
just like how anaconda does it. Don't include it, but allow it to be
brought in via deps. Because %packages can have --exclude statements it
is easy to fully exclude something from being brought in.


If that's not how pungi is currently working, sounds like either a bug
or a feature change after I stopped maintaining it.


--
Help me fight child abuse: http://tinyurl.com/jlkcourage

- jlk
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

Pungi and anaconda interpret %packages differently
 

On Fri, Aug 03, 2012 at 10:49:44AM -0700, Jesse Keating wrote:

> That said, I think when I originally coded pungi, I wanted - to work
> just like how anaconda does it. Don't include it, but allow it to be
> brought in via deps. Because %packages can have --exclude statements it
> is easy to fully exclude something from being brought in.
>
> If that's not how pungi is currently working, sounds like either a bug
> or a feature change after I stopped maintaining it.

That's not how pungi is currently working, a "minus-package" seems to
unconditionally exclude the package.

I don't see what the --exclude statement would do in %packages in a
kickstart file. It is also not listed in the anaconda documentation:

http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_3._Package_Selection

However, the "minus-package" statement is (for anaconda) described as

"You can also specify which packages not to install from the default
package list"

which is certainly not how pungi is handling it now.

I think I'll file a bug and see what the pungi maintainers think.

--
-- Jos Vos <jos@xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys

Pungi and anaconda interpret %packages differently
 

On 08/03/2012 11:18 AM, Jos Vos wrote:

I don't see what the --exclude statement would do in %packages in a
kickstart file. It is also not listed in the anaconda documentation:

http://fedoraproject.org/wiki/Anaconda/Kickstart#Chapter_3._Package_Selection



My bad. I meant the repo line can take --excludepkgs
http://fedoraproject.org/wiki/Anaconda/Kickstart#repo which is how one
would forcefully prevent a package from being included.


--
Help me fight child abuse: http://tinyurl.com/jlkcourage

- jlk
--
buildsys mailing list
buildsys@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys