[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Feedback about the cdd-dev package and more...

|--==> Sergio Talens-Oliag writes:

  ST> [1  <text/plain; us-ascii (quoted-printable)>]
  ST> El Thu, Dec 02, 2004 at 08:52:26AM +0100, Andreas Tille va escriure:
  >>On Wed, 1 Dec 2004, Andreas Tille wrote:
  >>>> more than once on this list). The current cdd-dev package only supports
  >>>> metapackages.
  >>>The packages in "sarge/sid" only support meta packages but you are not
  >>>supposed to use thesie because I just do not want to make untested software
  >>>its way into Sarge.
  >>Uhm, sorry, Sergio was right.  I just noticed that I did not yet uploaded
  >>cdd-dev 0.3.10 (from SVN) which supports tasksel.  This version has still
  >>some problems, but if you are looking for tasksel support - just give
  >>the SVN version a try (and fix the remaining problems).
  >>(If the SVN mail interface would have worked you all would have noticed this
  >>enhancement ... :-( )

  ST>   Well, I was working with the unstable packages installed on my system but
  ST>   looking at the svn source for some things, so I was not doing it the right
  ST>   way anyway.
  ST>   I'll build the svn packages and work with them for everything, and if I
  ST>   modify anything I'll put it on the svn repository.

  ST>   One question... are you tagging the packages? I'm using the svn-builpackage
  ST>   tool for my own packages and I believe it is quite useful, give it a try and
  ST>   if everybody agrees we could store the cdd-dev package in a compatible
  ST>   format, just to be able to branch and merge in a common way (I would like to
  ST>   work on a branch to implement new features, mainly to be able to break some
  ST>   things while developing without having to worry about other people using the
  ST>   current system).

I use svn-buildpackage  too. Quite good. We  shall really go for it. I
usually inject my packages with:

svn-inject package_0.1-1.dsc svn://server/repo

which  automatically  creates the  trunk  and tags   directory in  the
repository following the schema:


I  don't  know exactly how  we  could  migrate the  existent structure



Reply to: