FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux Pacman Development

 
 
LinkBack Thread Tools
 
Old 01-11-2008, 10:32 AM
"Roman Kyrylych"
 
Default etc: remove Arch-specific mirrorlist from repo

2008/1/11, Roman Kyrylych <roman.kyrylych@gmail.com>:
> 2008/1/11, Dan McGee <dan@archlinux.org>:
> > We shouldn't have the stock config be Arch specific for a few reasons:
> >
> > * Although it is our package, others should be able to use it
> > * Keeping the mirrorlist coupled to the pacman package makes it hard to push
> > updates to users without releasing a new copy of the pacman source
> >
> > Signed-off-by: Dan McGee <dan@archlinux.org>
> > ---
> > In all our other removals of things before 3.1.0, I probably should have done
> > this too. I'm debating whether to queue this up for 3.1.1 or 3.2.0. I'd
> > appreciate any input you guys have on this.
> >
> > This is the last thing in the code that is still tied tightly to Arch. I think
> > a seperate 'core/mirrorlist' package would make a lot more sense here, or at
> > least bundle it with filesystem or something. However, being its own package
> > would be ideal becuase it could be version bumped at any time.
> >
>
> I think we can close FS#5885 after this (which means "yeah, bring it on!"). ;-)
> I think separate mirrorlist package is better than merging it with
> filesystem package
> - it will be more clear to users what pacman is trying to update.
> Of course, mirrorlist should be in a backup array. If user is
> satisfied with his/her (sorted) mirrorlist - he/she can just delete
> mirrorlist.pacnew.
> And 3.1.1 is perfectly fine for this, no need to wait for 3.2.

Emmm... I've just noticed you've removed Arch-specific changes from
pacman.conf too. This is good, but I think we need to have pacman.conf
useable by default.
So I suggest just adding our current pacman.conf to CVS and replace
distro-independent pacman.conf during the packaging stage.
Having pacman.conf in mirrorlist package is not a good idea IMO.

--
Roman Kyrylych (*оман Кирилич)
_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 01-11-2008, 11:19 AM
Xavier
 
Default etc: remove Arch-specific mirrorlist from repo

On Jan 11, 2008 12:32 PM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
>
> Emmm... I've just noticed you've removed Arch-specific changes from
> pacman.conf too. This is good, but I think we need to have pacman.conf
> useable by default.
> So I suggest just adding our current pacman.conf to CVS and replace
> distro-independent pacman.conf during the packaging stage.
> Having pacman.conf in mirrorlist package is not a good idea IMO.
>


Funny, I missed that part too. I am also curious how pacman.conf would
be handled then.

_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 01-11-2008, 11:25 AM
"Roman Kyrylych"
 
Default etc: remove Arch-specific mirrorlist from repo

2008/1/11, Xavier <shiningxc@gmail.com>:
> On Jan 11, 2008 12:32 PM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
> >
> > Emmm... I've just noticed you've removed Arch-specific changes from
> > pacman.conf too. This is good, but I think we need to have pacman.conf
> > useable by default.
> > So I suggest just adding our current pacman.conf to CVS and replace
> > distro-independent pacman.conf during the packaging stage.
> > Having pacman.conf in mirrorlist package is not a good idea IMO.
> >
>
>
> Funny, I missed that part too. I am also curious how pacman.conf would
> be handled then.

I guess pacman.conf in CVS and this in pacman's PKGBUILD:
install -Dm644 pacman.conf $startdir/pkg/etc/pacman.conf

--
Roman Kyrylych (*оман Кирилич)
_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 01-11-2008, 11:48 AM
"Dan McGee"
 
Default etc: remove Arch-specific mirrorlist from repo

On Jan 11, 2008 6:25 AM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
> 2008/1/11, Xavier <shiningxc@gmail.com>:
> > On Jan 11, 2008 12:32 PM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
> > >
> > > Emmm... I've just noticed you've removed Arch-specific changes from
> > > pacman.conf too. This is good, but I think we need to have pacman.conf
> > > useable by default.
> > > So I suggest just adding our current pacman.conf to CVS and replace
> > > distro-independent pacman.conf during the packaging stage.
> > > Having pacman.conf in mirrorlist package is not a good idea IMO.
> > >
> >
> >
> > Funny, I missed that part too. I am also curious how pacman.conf would
> > be handled then.
>
> I guess pacman.conf in CVS and this in pacman's PKGBUILD:
> install -Dm644 pacman.conf $startdir/pkg/etc/pacman.conf

Yes.

Step back for a second and look at it this way. With any package, we
normally install our own conf file if the out-of-box one is not usable
or does not have sane defaults for Arch Linux. Pacman should be no
different.

Having a pacman.conf in CVS is absolutely fine, and this wouldn't
require a whole new release of pacman just to satisfy the addition or
removal of repositories. There should be *no* Arch Linux specifics in
the code that are not reasonable defaults for everyone.

-Dan

_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 01-11-2008, 03:48 PM
eliott
 
Default etc: remove Arch-specific mirrorlist from repo

On 1/11/08, Dan McGee <dpmcgee@gmail.com> wrote:
> On Jan 11, 2008 6:25 AM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
> > 2008/1/11, Xavier <shiningxc@gmail.com>:
> > > On Jan 11, 2008 12:32 PM, Roman Kyrylych <roman.kyrylych@gmail.com> wrote:
> > > >
> > > > Emmm... I've just noticed you've removed Arch-specific changes from
> > > > pacman.conf too. This is good, but I think we need to have pacman.conf
> > > > useable by default.
> > > > So I suggest just adding our current pacman.conf to CVS and replace
> > > > distro-independent pacman.conf during the packaging stage.
> > > > Having pacman.conf in mirrorlist package is not a good idea IMO.
> > > >
> > >
> > >
> > > Funny, I missed that part too. I am also curious how pacman.conf would
> > > be handled then.
> >
> > I guess pacman.conf in CVS and this in pacman's PKGBUILD:
> > install -Dm644 pacman.conf $startdir/pkg/etc/pacman.conf
>
> Yes.
>
> Step back for a second and look at it this way. With any package, we
> normally install our own conf file if the out-of-box one is not usable
> or does not have sane defaults for Arch Linux. Pacman should be no
> different.
>
> Having a pacman.conf in CVS is absolutely fine, and this wouldn't
> require a whole new release of pacman just to satisfy the addition or
> removal of repositories. There should be *no* Arch Linux specifics in
> the code that are not reasonable defaults for everyone.

Just to clarify, do you mean "no arch specific code" in the pacman
release tarballs, not the archlinux pacman package. Correct?

I agree. The pacman project is an arch 'sponsored' project, but it
isn't designed soley for arch. These types of changes should make it
easier for other distributions, like frugalware for example, to
package it up and use it -- I would think.

In theory, at some time in the future, I imagine the pacman devs
wouldn't even need to be the ones to own the arch pacman package. It
just works out well that way right now.

_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 01-11-2008, 04:27 PM
"Aaron Griffin"
 
Default etc: remove Arch-specific mirrorlist from repo

On Jan 11, 2008 10:48 AM, eliott <eliott@cactuswax.net> wrote:
> I agree. The pacman project is an arch 'sponsored' project, but it
> isn't designed soley for arch. These types of changes should make it
> easier for other distributions, like frugalware for example, to
> package it up and use it -- I would think.

That's correct. A large chunk of recent changes have been made with
this in mind.

Dan, I agree here, as long as the default pacman.conf has SOMETHING by
way of example, we can just replace it in the package like everything
else.

_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 01-11-2008, 04:30 PM
"Dan McGee"
 
Default etc: remove Arch-specific mirrorlist from repo

On Jan 11, 2008 11:27 AM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
> On Jan 11, 2008 10:48 AM, eliott <eliott@cactuswax.net> wrote:
> > I agree. The pacman project is an arch 'sponsored' project, but it
> > isn't designed soley for arch. These types of changes should make it
> > easier for other distributions, like frugalware for example, to
> > package it up and use it -- I would think.
>
> That's correct. A large chunk of recent changes have been made with
> this in mind.
>
> Dan, I agree here, as long as the default pacman.conf has SOMETHING by
> way of example, we can just replace it in the package like everything
> else.

So in reference to the original patch, what should I do? Add an
example sync repository section, all commented out?

-Dan

_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 
Old 01-11-2008, 07:37 PM
"Aaron Griffin"
 
Default etc: remove Arch-specific mirrorlist from repo

On Jan 11, 2008 11:30 AM, Dan McGee <dpmcgee@gmail.com> wrote:
>
> On Jan 11, 2008 11:27 AM, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
> > On Jan 11, 2008 10:48 AM, eliott <eliott@cactuswax.net> wrote:
> > > I agree. The pacman project is an arch 'sponsored' project, but it
> > > isn't designed soley for arch. These types of changes should make it
> > > easier for other distributions, like frugalware for example, to
> > > package it up and use it -- I would think.
> >
> > That's correct. A large chunk of recent changes have been made with
> > this in mind.
> >
> > Dan, I agree here, as long as the default pacman.conf has SOMETHING by
> > way of example, we can just replace it in the package like everything
> > else.
>
> So in reference to the original patch, what should I do? Add an
> example sync repository section, all commented out?

I'd add a few examples. servers listed, some using $repo, some not and
add an Include directive... not a real section but some comments
describing them (see /etc/mkinitcpio.conf for how I like to do this
stuff)

_______________________________________________
pacman-dev mailing list
pacman-dev@archlinux.org
http://archlinux.org/mailman/listinfo/pacman-dev
 

Thread Tools




All times are GMT. The time now is 01:26 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org