Ashok Gautham wrote:
> Can AUR have something like a watch list. It would be useful.
>
> I find that at times I forget that I flagged a package out of date. After a
> long time, I finally remember it and then go and check it out again.
> Instead, if we had something like "My watchlist", I would
2009/4/12 Xyne :
> You could write a script to parse the output from
> http://aur.archlinux.org/rpc.php?type=search&arg=
>
> That includes whether is outdated, the number of votes, version
> number, etc. If you want comments then I think you need to scrape the
> web page.
>
The code for seeing co
Hi,
Just let me know if there is a more appropriate place for this and
sorry for all eventual noobishness.
1) Why are the "x86_64" and "i686" tags stripped out of package names?
Wouldn't it make more sense to use these tags to determine the port
when uploading binary packages to community? This
Xyne wrote:
Hi,
Just let me know if there is a more appropriate place for this and
sorry for all eventual noobishness.
1) Why are the "x86_64" and "i686" tags stripped out of package names?
Wouldn't it make more sense to use these tags to determine the port
when uploading binary packages to co
> > 3) Is there any way to avoid re-uploading a package when changing the
> > PKGBUILD if the changes have no effect on the built package (e.g.
> > appending packages to the depends array)?
> >
>
> Adding more depends does alter the package... But you can always alter
> the package in cvs an
Xyne wrote:
3) Is there any way to avoid re-uploading a package when changing the
PKGBUILD if the changes have no effect on the built package (e.g.
appending packages to the depends array)?
Adding more depends does alter the package... But you can always alter
the package in cvs and
On Sun, Apr 12, 2009 at 1:07 PM, Xyne wrote:
>
> You could write a script to parse the output from
> http://aur.archlinux.org/rpc.php?type=search&arg=
>
> That includes whether is outdated, the number of votes, version
> number, etc. If you want comments then I think you need to scrape the
> web
2009/4/12 Xyne :
[ snip ]
> Wouldn't it make more sense to use these tags to determine the port
> when uploading binary packages to community? This would also be useful
> for uploading "any" packages (which I suppose need to be uploaded
> twice).
Just to clarify, currently [community] does not sup
I have just updated and started to maintain the python-apsw package (the
current version in AUR was from Oct 2007, when the last version is from Feb
2009)
This package is needed for the tribler package (bittorrent client)
Please let me know if you use this library and therefore whether the packag
On Sun, Apr 12, 2009 at 06:06, Ashok Gautham wrote:
> On Sun, Apr 12, 2009 at 1:07 PM, Xyne wrote:
> I think I am not clear. Well. I meant some link on the site. Something like
> My Packages. Once I log in, I should have a list of packages I am watching
> over. Something like
>
> http://wiki.ans
Firmicus wrote:
> I offer the following packages for adoption to any interested TU:
...
> libxml-perl
> perl-file-nfslock
> perl-freezethaw
Adopted.
-- Chris
2009/4/12 Juan Miguel Cejuela :
> I have just updated and started to maintain the python-apsw package (the
> current version in AUR was from Oct 2007, when the last version is from Feb
> 2009)
>
> This package is needed for the tribler package (bittorrent client)
>
> Please let me know if you use t
Allan McRae wrote:
> The .PKGINFO file is created by makepkg and compressed inside the
> package. When you upload a package to the server, this file is
> extracted and an entry is made for the pacman database using this
> information. So any change that alters the .PKGINFO file or any
> ins
On Sun, Apr 12, 2009 at 11:23:07PM +0200, Xyne wrote:
> Allan McRae wrote:
>
> > The .PKGINFO file is created by makepkg and compressed inside the
> > package. When you upload a package to the server, this file is
> > extracted and an entry is made for the pacman database using this
> > infor
14 matches
Mail list logo
