Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   ArchLinux Development (http://www.linux-archive.org/archlinux-development/)
-   -   pacman tag support (initial patch attached) (http://www.linux-archive.org/archlinux-development/146088-pacman-tag-support-initial-patch-attached.html)

"Ronald van Haren" 08-20-2008 09:29 PM

pacman tag support (initial patch attached)
 
Hi guys!

Can someone give me write access to pacman git (Dan?), so I don't have
to send every patch to the list :)

Anyways, I took a bit of time to start writing tag support for pacman
and makepkg, which is usefull now we don't have categories anymore
like we had before (and still have for community).
You should be warned that I did not yet do a code cleanup (that will
come when all features are in), but it is starting to get a bit messy
with patch files on my local box so I like to commit.

I guess the patch should work both against pacman git and 3.2.0 at the moment.

How does it work?

in PKGBUILD, define a field called tags, for example:
tags=('gnome' 'gtk' 'network' 'messenger')

compile with makepkg as usual. Install with pacman with attached patch applied.
the tags field should show up in 'pacman -Qi'.

Further you can search the local database (only long option is
working, short option not yet, have to look into it). You can search
with (multiple tags works):
pacman -Q --tags gnome

My little TODO list for next pacman release:

- be able to search for tags in the repos
- get short options working
- write proper documentation
- cleanup

So please patch it into git, or better give me access. Any comments are welcome.

Regards,

Ronald

"Aaron Griffin" 08-21-2008 05:31 AM

pacman tag support (initial patch attached)
 
On Wed, Aug 20, 2008 at 4:29 PM, Ronald van Haren <pressh@gmail.com> wrote:
> Hi guys!
>
> Can someone give me write access to pacman git (Dan?), so I don't have
> to send every patch to the list :)

For the record, this is on purpose. git makes it so that it's very
easy to send patches and manage your own repo. I am totally
comfortable with Dan managing this. If you use git-format-patch and
git-send-email, emailing patches to an ML is a breeze, and applying
them (with git-am) is too.

I'd still suggest sending this to the pacman-dev ML, as many of the
active pacman people are there and not really official developers

"Dan McGee" 08-21-2008 05:45 AM

pacman tag support (initial patch attached)
 
On Thu, Aug 21, 2008 at 12:31 AM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
> On Wed, Aug 20, 2008 at 4:29 PM, Ronald van Haren <pressh@gmail.com> wrote:
>> Hi guys!
>>
>> Can someone give me write access to pacman git (Dan?), so I don't have
>> to send every patch to the list :)
>
> For the record, this is on purpose. git makes it so that it's very
> easy to send patches and manage your own repo. I am totally
> comfortable with Dan managing this. If you use git-format-patch and
> git-send-email, emailing patches to an ML is a breeze, and applying
> them (with git-am) is too.
>
> I'd still suggest sending this to the pacman-dev ML, as many of the
> active pacman people are there and not really official developers

I guess I can't blame new developers for their gusto, so no hard
feelings, but getting commit access to pacman.git is not quite that
easy. Talk to the rest of the "development staff" on the pacman-dev
mailing list and you will find 95% of contributions go through the
list, even those of mine that are not trivial. Sending patches to the
list enables us to do easy peer review, and this process has been
tried and tested with Linux kernel development for some time, so it
isn't just for small projects.

As I believe numerous people have said, pacman-dev is a great place to
bring these kind of things up and you will have a much more talkative
audience there. In addition, http://archlinux.org/pacman/HACKING.html
and http://archlinux.org/pacman/submitting-patches.html are helpful
reads.

-Dan

"Ronald van Haren" 08-21-2008 08:16 AM

pacman tag support (initial patch attached)
 
sorry for not knowing, Xavier already told me about it. Next time I'll
first check if such a mailinglist does exist before bothering you ;)

ronald

On 8/21/08, Dan McGee <dpmcgee@gmail.com> wrote:
> On Thu, Aug 21, 2008 at 12:31 AM, Aaron Griffin <aaronmgriffin@gmail.com>
> wrote:
>> On Wed, Aug 20, 2008 at 4:29 PM, Ronald van Haren <pressh@gmail.com>
>> wrote:
>>> Hi guys!
>>>
>>> Can someone give me write access to pacman git (Dan?), so I don't have
>>> to send every patch to the list :)
>>
>> For the record, this is on purpose. git makes it so that it's very
>> easy to send patches and manage your own repo. I am totally
>> comfortable with Dan managing this. If you use git-format-patch and
>> git-send-email, emailing patches to an ML is a breeze, and applying
>> them (with git-am) is too.
>>
>> I'd still suggest sending this to the pacman-dev ML, as many of the
>> active pacman people are there and not really official developers
>
> I guess I can't blame new developers for their gusto, so no hard
> feelings, but getting commit access to pacman.git is not quite that
> easy. Talk to the rest of the "development staff" on the pacman-dev
> mailing list and you will find 95% of contributions go through the
> list, even those of mine that are not trivial. Sending patches to the
> list enables us to do easy peer review, and this process has been
> tried and tested with Linux kernel development for some time, so it
> isn't just for small projects.
>
> As I believe numerous people have said, pacman-dev is a great place to
> bring these kind of things up and you will have a much more talkative
> audience there. In addition, http://archlinux.org/pacman/HACKING.html
> and http://archlinux.org/pacman/submitting-patches.html are helpful
> reads.
>
> -Dan
>


All times are GMT. The time now is 08:16 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.