Well, i'm not pretty sure but when I used to make a custom package
with PKGBUILD and succesfully created the package tarball, subsequent
calls to makepkg without force flag ends with a
package_foo_already_exists_use_force_flag message...

2006/4/23, Mircea Bardac <[EMAIL PROTECTED]>:
> Hi everybody,
>
> I was working today on some PKGBUILDs and remembered about the new options
> added to makepkg. A quick look in man makepkg showed me:
>
> --- man makepkg ---
> options
>    This array allows you to override some of makepkg's default behaviour when
> building packages. To set an option, just include the option name in the
> options array.
>
> Available Options:
> FORCE - force the package to be upgraded by --sysupgrade, even if its an older
> version.
> KEEPDOCS - do not remove /usr/share/doc and /usr/share/info directories.
> NOSTRIP - do not strip debugging symbols from binaries and libraries.
> -- end ---
>
> Now, everything looked shiny as I've noticed the NOSTRIP option. In the
> process of building a package I am constantly forcing makepkg to overwrite
> the package in the current directory using -f.
>
> The FORCE option got me thinking. After some pondering I got to the conclusion
> that it certainly doesn't have to anything with the PKGBUILD itself and it
> only affects PACMAN... isn't this so?
>
> The only people using this might be package managers forcing users to
> downgrade by adding a package in the repository tagged with FORCE (btw, is
> this the only tag appliable to a package?)
>
> If it is so, I would recommend making another array of options for
> pacman_options next to the makepkg_options (and name then accordingly) in
> order to avoid confusions like above. If force works like I think it does, it
> has no reason to stay next to the other 2 options.
>
> I am aware that Arch should remain KISS and this brings another option to the
> discussion, but mixing pacman and makepkg options is not very easy to
> understand, IMO.
>
>
> Thanks,
>
> Mircea
> /IceRAM
>
> --
> http://mircea.bardac.net
>
>
> _______________________________________________
> arch mailing list
> [email protected]
> http://www.archlinux.org/mailman/listinfo/arch
>
>
>
>


--
Dani
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch

Reply via email to