[pacman-dev] [PATCH] makepkg: Add EXTRAVERSION field to package filenames
allan at archlinux.org
Fri Oct 23 08:52:13 EDT 2009
Anders Bergh wrote:
> On Fri, Oct 23, 2009 at 02:37, Allan McRae <allan at archlinux.org> wrote:
>> Anders Bergh wrote:
>>> >From 92f67cdcff4cbec3c5c9d6b0ca17a6f71fdf87b9 Mon Sep 17 00:00:00 2001
>>> From: Anders Bergh <anders1 at gmail.com>
>>> Date: Fri, 23 Oct 2009 00:11:05 +0200
>>> Subject: [PATCH] makepkg: Add EXTRAVERSION field to package filenames.
>>> This is intended
>>> for packages compiled to run on another operating system than Linux,
>>> such as cygwin or Darwin. It is set using --with-pkg-extra-version.
>>> The package filename format is as follows:
>>> Signed-off-by: Anders Bergh <anders1 at gmail.com>
>> I'm not sure why this is needed and will need more explanation... is this
>> so foo-1-1-i686.pkg.tar.gz does not have the same file name on (e.g.)
>> windows and linux? Surely they would be in different repos and the name
>> conflict will never arrive.
> I am working on a basic port of Arch to another kernel, and I thought
> it would be nice to have those packages make it obvious they're not
> going to work on Linux. For instance, if someone were to Google the
> package filenames and find my repository they might not be able to
> tell that it's not going to work on their system.
> But I do agree it's not strictly necessary.
I have actually been thinking about this as I have a (somewhat working)
i686-pc-kfreebsd-gnu cross-compuler and wondered how I would distinguish
the i686's. I also made and i686-pc-mingw32 compiler for yet another
i686... Then I realized that you can always make
CARCH="i686-bsd".However, if you I provide a repo, and people are
downloading packages, they should know whether they are good for their
install before trying to install them.
tl;dr: I see the issue but do not know if it is necessary to solve.
Any other opinions?
More information about the pacman-dev