headers
NetBSD source update | 1 Jun 2012 03:10
Picon

daily pkgsrc CVS update output


Updating pkgsrc tree:
? pkgsrc/INDEX
? pkgsrc/README-IPv6.html
? pkgsrc/README-all.html
? pkgsrc/net/wget/work
P pkgsrc/audio/amarok/Makefile
P pkgsrc/databases/db5/Makefile
P pkgsrc/databases/db5/PLIST
P pkgsrc/databases/db5/distinfo
U pkgsrc/databases/db5/patches/patch-src_dbinc_atomic.h
P pkgsrc/databases/sdbm/distinfo
P pkgsrc/databases/sdbm/patches/patch-ai
P pkgsrc/devel/Makefile
P pkgsrc/devel/glib2/options.mk
P pkgsrc/devel/libusb-compat/Makefile
U pkgsrc/devel/libusb1/buildlink3.mk
P pkgsrc/devel/p5-Contextual-Return/Makefile
U pkgsrc/devel/p5-Contextual-Return/distinfo
U pkgsrc/devel/p5-Test-DistManifest/DESCR
U pkgsrc/devel/p5-Test-DistManifest/Makefile
U pkgsrc/devel/p5-Test-DistManifest/distinfo
P pkgsrc/doc/CHANGES-2010
P pkgsrc/doc/CHANGES-2012
P pkgsrc/doc/TODO
P pkgsrc/emulators/mess/Makefile
P pkgsrc/emulators/mess/PLIST
P pkgsrc/games/moria/distinfo
U pkgsrc/games/moria/patches/patch-source_files_c
P pkgsrc/graphics/darktable/Makefile
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thomas Klausner | 1 Jun 2012 15:36
Picon

cvs import -> cvs add

Hi!

AFAIK, we use 'cvs import' for adding new packages since at the
beginning of pkgsrc, the first packages came from FreeBSD ports and
the idea was to sync them from there regularly. This never happened.

Since 'cvs import' is much more error-prone than 'cvs add' and doesn't
provide any additional features we need, I suggest we switch to using
'cvs add'.

 Thomas
Permalink | Reply | 20 comments |
headers
David Holland | 1 Jun 2012 16:01
Picon

Re: cvs import -> cvs add

On Fri, Jun 01, 2012 at 03:36:40PM +0200, Thomas Klausner wrote:
 > AFAIK, we use 'cvs import' for adding new packages since at the
 > beginning of pkgsrc, the first packages came from FreeBSD ports and
 > the idea was to sync them from there regularly. This never happened.
 > 
 > Since 'cvs import' is much more error-prone than 'cvs add' and doesn't
 > provide any additional features we need, I suggest we switch to using
 > 'cvs add'.

+1

--

-- 
David A. Holland
dholland <at> netbsd.org
Permalink | Reply | 0 comments |
headers
Benny Siegert | 1 Jun 2012 16:07
Picon
Gravatar

Re: cvs import -> cvs add


> Since 'cvs import' is much more error-prone than 'cvs add' and doesn't
> provide any additional features we need, I suggest we switch to using
> 'cvs add'.

Excellent suggestion. I'm in. 

--Benny.
Permalink | Reply | 0 comments |
headers
Julio Merino | 1 Jun 2012 16:20
Picon

Re: cvs import -> cvs add

On Fri, Jun 1, 2012 at 9:36 AM, Thomas Klausner <wiz <at> netbsd.org> wrote:
> Hi!
>
> AFAIK, we use 'cvs import' for adding new packages since at the
> beginning of pkgsrc, the first packages came from FreeBSD ports and
> the idea was to sync them from there regularly. This never happened.
>
> Since 'cvs import' is much more error-prone than 'cvs add' and doesn't
> provide any additional features we need, I suggest we switch to using
> 'cvs add'.

Makes sense; +1.

--

-- 
Julio Merino /  <at> jmmv
Permalink | Reply | 0 comments |
headers
Jonathan Perkin | 1 Jun 2012 16:31
Favicon

Multi-architecture package support

Hi,

For anyone interested, I have an initial implementation of
multi-architecture packages.  This is something we need at Joyent to
avoid having to provide package sets for both 32bit and 64bit, and I
figured it might be useful for other Solaris users too.

Ultimately it'd be great to have this merged into pkgsrc, however it
does require modifications to any package for which multi-architecture
support is desired.  Thus I'd appreciate any feedback on whether there
is any demand for this feature, or less intrusive ways of implementing
it.  One thought is that it may potentially be useful on OSX to
provide fat binaries (32+64 x86, rather than x86+ppc), and it should
be relatively straight-forward to add such functionality.

The commit and a description is here:

  https://github.com/joyent/pkgsrc/commit/d64f78a9aecb10b89677c9fec7d7fd6fb32dc46d

Thanks,

--

-- 
Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com
Permalink | Reply | 4 comments |
headers
Ryo ONODERA | 1 Jun 2012 19:53
Picon

Re: cvs import -> cvs add

Hi,

From: Thomas Klausner <wiz <at> NetBSD.org>, Date: Fri, 1 Jun 2012 15:36:40 +0200

> Hi!
> 
> AFAIK, we use 'cvs import' for adding new packages since at the
> beginning of pkgsrc, the first packages came from FreeBSD ports and
> the idea was to sync them from there regularly. This never happened.
> 
> Since 'cvs import' is much more error-prone than 'cvs add' and doesn't
> provide any additional features we need, I suggest we switch to using
> 'cvs add'.

"cvs add" only?
"cvs import" with pkglint and wip/import-package.sh script is easy to use.
I feel that '"cvs add" and "cvs import" are acceptable' make sense.

--

-- 
Ryo ONODERA // ryo_on <at> yk.rim.or.jp
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3
Permalink | Reply | 2 comments |
headers
Thomas Klausner | 1 Jun 2012 21:11
Picon

Re: cvs import -> cvs add

On Sat, Jun 02, 2012 at 02:53:46AM +0900, Ryo ONODERA wrote:
> "cvs add" only?

Yes.

> "cvs import" with pkglint and wip/import-package.sh script is easy to use.
> I feel that '"cvs add" and "cvs import" are acceptable' make sense.

There'll be a switchover time when both is allowed to get users
accustomed to it, but I think we should only recommend one of the two.
 Thomas
Permalink | Reply | 1 comment |
headers
Ryo ONODERA | 1 Jun 2012 21:15
Picon

Re: cvs import -> cvs add

From: Thomas Klausner <wiz <at> NetBSD.org>, Date: Fri, 1 Jun 2012 21:11:09 +0200

> On Sat, Jun 02, 2012 at 02:53:46AM +0900, Ryo ONODERA wrote:
>> "cvs add" only?
> 
> Yes.
> 
>> "cvs import" with pkglint and wip/import-package.sh script is easy to use.
>> I feel that '"cvs add" and "cvs import" are acceptable' make sense.
> 
> There'll be a switchover time when both is allowed to get users
> accustomed to it, but I think we should only recommend one of the two.

I see.
Consistent handling of repository is important.
We should use one procedure.

Thank you.

--

-- 
Ryo ONODERA // ryo_on <at> yk.rim.or.jp
PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3
Permalink | Reply | 0 comments |
headers
NetBSD source update | 2 Jun 2012 04:22
Picon

daily pkgsrc CVS update output


Updating pkgsrc tree:
? pkgsrc/INDEX
? pkgsrc/README-IPv6.html
? pkgsrc/README-all.html
? pkgsrc/net/wget/work
P pkgsrc/archivers/gtar-base/Makefile
P pkgsrc/archivers/gtar-base/PLIST
P pkgsrc/converters/ruby-unf_ext/Makefile
U pkgsrc/converters/ruby-unf_ext/distinfo
P pkgsrc/databases/gramps3/Makefile
P pkgsrc/databases/gramps3/PLIST
U pkgsrc/databases/gramps3/distinfo
cvs update: pkgsrc/databases/gramps3/patches/patch-aa is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-ab is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-ac is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-ad is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-ae is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-ag is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-ah is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-ai is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-aj is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-ak is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-al is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-am is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-an is no longer in the repository
cvs update: pkgsrc/databases/gramps3/patches/patch-ao is no longer in the repository
U pkgsrc/databases/gramps3/patches/patch-ba
P pkgsrc/databases/ruby-sequel/Makefile
P pkgsrc/databases/ruby-sequel/PLIST
(Continue reading)

Permalink | Reply | 0 comments |

Gmane