Hi,
I have been working on an Arch fork for the past several months, and
thus have been following Arch developments closely. I noticed this
commit (
http://projects.archlinux.org/gitweb.cgi?p=pacman.git;a=commit;h=b8a66d68593d1f267c3bb8cd8943724711626903
), where OpenSSL replaces the usage of md5
7:12 PM, Xavier <[EMAIL PROTECTED]> wrote:
> Teran McKinney wrote:
>> Hi,
>>
>> I have been working on an Arch fork for the past several months, and
>> thus have been following Arch developments closely. I noticed this
>> commit (
>> http://projects.arc
Perhaps testing for executability instead would be better?
Regardless, I like the idea.
--Teran (sega01)
On Sat, Jul 26, 2008 at 14:43, Mark Constable <[EMAIL PROTECTED]> wrote:
> Just a suggestion. If this was the last line in /etc/makepkg.conf
> then it would allow anyone to append functions t
Hey,
While revamping eleutherNet's ( http://eleuther.net ) DNS setup and
giving it external IPv6 connectability, I found Pacman's sync server
resolving method to be problematic during testing. Pacman 3.2.0 seems
to only try the primary nameserver when resolving a server to sync to.
The common (tho
Wouldn't this break package extensions that are not *.tar.{gz,bz2}? I
personally do not like this, as my Arch fork uses .ipkg (I find
pkg.tar.$COMPRESSION very ugly, IMHO). Perhaps tar could simply tar
the archive and a setting in makepkg.conf would allow for any method
of compression? Example:
ma
Hey,
I've planned out a set of changes I want to try with Pacman and
Makepkg. Most deal with creating a source repository setup that would
store source files as their sha512sums, but that isn't related to
this. Another thing that I want to do is have a "shared" repository
for non-architecture spec
On Mon, Sep 29, 2008 at 00:14, Dan McGee <[EMAIL PROTECTED]> wrote:
> On Sat, Sep 27, 2008 at 3:03 PM, Teran McKinney <[EMAIL PROTECTED]> wrote:
>> PS: I think that the stock makepkg should default to arch=(any) if
>> $arch is not set. I do this in Icadyptes, a
Seems a little more concise to me, but I personally think that the
install script should be commented out (if it has a default value).
Maybe arch=('any') should be default? Would make life easier for
non-i686/x86_64 maintainers, and is generally much more truthful.
Cheers,
Teran (sega01)
On Sat,
I like the idea of GPG signed repositories, but they are just about
useless if they are signing MD5s. MD5 is very insecure, but good for
normal file integrity checking. Can Pacman use SHA-256 or similiar?
Another thing to watch out for is malicious publication of old
repositories with old and vulne
so use .ipkg for the package extension, but I don't think
any of this is very usable by the mainstream Pacman :-).
Thanks for the interest in my makepkg modifications. Let me know if you
have any comments, ideas, or suggestions.
Cheers,
Teran (sega01)
On Tue, 20 Jan 2009 14:58:50 +
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey,
I've personally ran into this before, but don't think that it is worth
"fixing" in the current Pacman setup. User error is usually the cause of
this, since an admin should always have adequate disk space before
installing new packages. Preventi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey,
This is already in Icadyptes' makepkg as runtimedeps=(). Not sure if
runtimedeps=() matches the PKGBUILD variable naming scheme as much, but
I would appreciate considering to use runtimedeps=() instead. Although
if you go with rundepends=(), I'
with arch=() implying arch=('any').
Cheers,
Teran
On Fri, 17 Apr 2009 04:27:42 +1000
Allan McRae wrote:
> Teran McKinney wrote:
> > Hey,
> >
> > This is already in Icadyptes' makepkg as runtimedeps=(). Not sure if
> > runtimedeps=() matches the PKGBUILD va
there. I think that it would be a much easier
and more thorough solution, although it does have some weaknesses on
edge cases, possibly. <http://gitweb.icadyptes.org>
Just wanted to suggest that. I know it's not integrated, but I think
it's a better long-term solution, personally.
T
14 matches
Mail list logo
